Timeout  when refreshing UWL

Hi
When we refresh the UWL, I get the following error message
" An error occurred while trying to connect to the provider ".
When I click on the details it says "Time out occured. Time taken is more than 30 seconds"
This error occurs only if the browser language is something other than English. Can anyone throw some light on this?
Regds
Thiru

Hi Maria,
The timeout is because when we use language other than the language in which the work items were created, then all the system tries to translate all workitems  in the UWL from theie original language and hence the timeout.
To solve this, you can set the "Timeout Value for the Connected Systems, in Seconds" under "Optional Universal Worklist Service Configuration" to a higher value (default is 30 seconds).
Regds
Thiru

Similar Messages

  • Refreshing UWL automaticly ?

    hi there,
    for a workflow i have to implement the (very user-unfriendly) UWL in our portal.
    there is a strange behaviour when i go to the 'inbox' of the UWL. i can't see all workitems,
    and i have a message on top which says 'waiting for refreshing'. as i have a german language
    system i don't know if this is the right english translation for this message.
    after a too long time (+- 30 seconds) the UWL has been refreshed, and i see all workitems.
    what is wrong there. how can i refresh automaticly ?
    best regards, Martin

    Hi Martin,
    these are two different settings
    - one for the service done in the background (service refresh time)
    - one for the UI. Concerning this you have to set the iView param "Wait duration for UI refresh while waiting for update".
    The first time the user logs on there is an auto refresh done, if the items are out of date. You can turn off the initial refresh by setting this property in the iView to 0.
    I think the reason for this was placemend of UWL iView on default homepage. If it is placed there every time a rfc to backend will be executed and may be some users will click straight forward to another portal page. The wait duration will avoid this.
    remind that this property will be used only for first call of UWL iview in current user session.
    If you want to refresh UWL list every time a user opens this iView you have to set up a additional invisible iview on the UWL page which will raise an EPCM event to force refresh.
    best regards,
    Thorsten

  • Return 504 Gateway TimeOut when access exchange service by domain/user and password

    hi,
    here is the scenario: a user of our app is in ntdev domain, and his exchange server located at apj.cloudmail.microsoft.com. our backend api is deployed at the Azure servers at US West.
    our api get 504 Gateway Timeout when calling the
    FindFolders API of exchangeService. does anyone know how to fix this issue? the following is the core code:
    var
    service = newExchangeService(ExchangeVersion.Exchange2010);
    service.Credentials =
    newNetworkCredential(username,
    password, domain);
    service.AutodiscoverUrl(emailAddress, RedirectionUrlValidationCallback);
    service.FindFolders(
    WellKnownFolderName.Root,
    newFolderView(1));

    That doesn't sound like its an EWS issue more an issue with the Network path your trying to traverse to the Exchange Server. My suggestion is that you test EWS using the EWSeditor
    https://ewseditor.codeplex.com/ (eg it sounds like you may have proxy server that expecting authentication etc.).
    Cheers
    Glen

  • Re: [iPlanet-JATO] Re: session timeout when not submitting to a handler

    Mark--
    I know what's happening here, but am curious about your approach. You said
    in an earlier email that you were generating links directly to JSPs, but
    from what you are describing, you are generating JATO-style links to access
    JATO pages. Nothing wrong with that, but there is a signficant difference.
    Actually, it just occurred to me, I'm wondering what your URLs look like.
    The way the request dispatching works in JATO is it ignores anything after
    an initial "." in the final part of the URL path. For example, a request
    for "/myapp/module1/MyPage.jsp" doesn't actually try to hit the JSP, instead
    it tries to hit the JATO page "/myapp/module1/MyPage".
    The end result is that you may think you are accessing a JSP directly, but
    are instead accessing a JATO page. The reason the request dispatching works
    this way is because it is illegal to access JATO JSPs directly, and there is
    actually a (disabled) JATO feature that piggybacks on the use of the
    dot-delimited URL.
    So, now I need to understand your intent. I wasn't really sure why you were
    generating direct JSP/page links to begin with. This works against the Type
    II architecture JATO uses, in which all JATO requests go back to the
    controller servlet.
    If you are trying to design something like a menu page, you may have thought
    that it was burdensome to create a number of HREF children, plus implement
    event handlers for each of them. This definitely would be burdensome beyond
    just a handful of links, but this is why JATO provides other mechanisms for
    doing what I'll call here "polymorphic HREFs".
    Assuming this menu page scenario, the easiest thing to do is to simply use
    one HREF child on the page, and add a value to it each time it is rendered
    that distinguishes it from the other instances on the page. In your event
    handler for the HREF, you simply check this value and use it to decide which
    page to forward to. You can add a value to an HREF or Button by using the
    "addExtraValue()" method. Or, if you are using JATO 1.2, you can add extra
    query string NVPs right in the JSP document using the "queryParams"
    attribute of the <jato:href> tag. Thus, your one HREFchild and event
    handler become "polymorphic" because what they do depends on the context in
    which they are invoked.
    Now, I still don't have confirmation that this is what you were trying to
    do, so until I do, let me explain the exception you're seeing. JATO assumes
    that when a request comes in for a page that includes the pageAttributes
    NVP, it is a request coming from a previously generated JATO page. Because
    of the way JATO works, this means that the request dispatching code should
    send the request back to the originally rendered page. For example, if Page
    A renders an HREF, which the user then activates, JATO sends the request
    back to Page A for handling. All of the HREFs and forms generated during
    rendering of Page A actually refer back to Page A, regardless of where those
    links or buttons actually pass the request in their event handlers/Command
    objects.
    So, what's happening when you include the pageAttributes in your HREFs is
    that JATO is assuming that a request is being sent to the target page, with
    the assumption that the target page has a mechanism in place to handle the
    request. This assumption relies on the specification of the "originator" of
    the request being specified in the request. For links/HREFs, the name and
    value of the HREF is sent along with the request. For forms, the name and
    value of the button that was pressed are sent in the request. JATO uses the
    presence of these name/value pairs to decide which event handler, or which
    Command object, to invoke to handle the request.
    The exception you are receiving is saying that there was no object on the
    target page that indicated it could handle the request. This is to be
    expected, since you have not specified a query parameter that indicates
    which CommandField child is responsible the request. However, this is where
    I see the disconnect, because that is not what I believe you were trying to
    do (as explained above).
    So now, given all the information above, can you tell me what you're trying
    to accomplish, and whether or not the info I've given you has helped you to
    design a mechanism more in line with a JATO approach? If not, given that I
    understand what you're trying to do, I can offer a more concrete solution.
    Todd
    ----- Original Message -----
    From: <Mark_Dubinsky@p...>
    Sent: Monday, November 05, 2001 2:54 PM
    Subject: [iPlanet-JATO] Re: session timeout when not submitting to a handler
    This is the exception we get:
    (And BTW, leaving a blank value for the pageAttributes doesn't help)
    [05/Nov/2001 17:49:18:4] error: <portalServlet.processRequest>
    javax.servlet.ServletException: The request was not be handled by the
    specified handler
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at
    javax.servlet.ServletException.<init>(ServletException.java:107)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.dispatchRequ
    est(Compiled Code)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.processReque
    st(Compiled Code)
    at
    com.putnaminvestments.bp.portal.portalServlet.processRequest(Compiled
    Code)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.doPost(Compi
    led Code)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.doGet(Compil
    ed Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code)
    at com.putnaminvestments.bp.bpServletBase.service(Compiled
    Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code)
    at
    com.netscape.server.servlet.servletrunner.ServletInfo.service(Compile
    d Code)
    at
    com.netscape.server.servlet.servletrunner.ServletRunner.execute(Compi
    led Code)
    at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
    at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Compiled Code)
    at java.lang.Thread.run(Compiled Code)
    --- In iPlanet-JATO@y..., "Todd Fast" <Todd.Fast@S...> wrote:
    Mark--
    Initially we tried to add the pageAttributes NVP as well, but that
    was
    causing an exception, so we stopped doing that.That's odd--what was the exception?
    Our problem now is that when the SessionTimes out it does not go
    to
    onSessionTimeout method as in processRequestMethod of the
    ApplicationServletBase it looks for pageAttributes. If it is notnull
    then only onSessionTimeOut method is called.This is sadly the only technique for determining if a session hastimed out
    and a new one been created, versus the initial creation of thesession.
    Is there any work around for this? Maybe you can suggest how topass
    the pageAttributes without causing the initial exception?Definitely--let me know what the exception was and I'll be able tosuggest
    something. However, it shouldn't really be any harder thanappending a
    "jato.pageAttributes=" empty NVP on the HREF.
    Todd
    Todd Fast
    Senior Engineer
    Sun/Netscape Alliance
    todd.fast@s...
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

    OK, here's what I'm trying to do: We have, like you said, a menu
    page. The pages that it goes to and the number of links are all
    variable and read from the database. In NetD we were able to create
    URLs in the form
    pgXYZ?SPIDERSESSION=abcd
    so this is what I'm trying to replicate here. So the URL that works
    is
    pgContactUs?GXHC_GX_jst=fc7b7e61662d6164&GXHC_gx_session_id_=cc9c6dfa5
    601afa7
    which I interpreted to be the equivalent of the old Netd way. Our
    javascript also loads other frames of the page in the same manner.
    And I believe the URL-rewritten frame sources of a frameset look like
    this too.
    This all worked except for the timeout problem. In theory we could
    rewrite all URLs to go to a handler, but that would be...
    inconvenient.

  • Error when refreshing WEBI report with Universe Connection Type "SSO"

    Hi Experts:
    We are trying to refresh the Webi report in Infoview with Universe Connection set as "Use Single Sign On when refreshing the report at view time", so that we can leverage SAP OLAP authorization variable from Bex Query which the Universe is built on.
    However got the error of "incomplete logon data" after all the configurations done following below blogs:
    SNC Part 1
    /people/ingo.hilgefort/blog/2009/07/03/businessobjects-enterprise-and-client-side-snc-part-1-of-2
    SNC Part 2
    /people/ingo.hilgefort/blog/2009/07/03/businessobjects-enterprise-and-client-side-snc-part-2-of-2
    We already have Win AD SSO to SAP setup, and in BO CMC, Win AD user is mapped to SAP user ID.
    The SNC settings are:
    - AD Account: service.test.bobj (all lower-letters)
    - 32-bit gsslib on the BO server, and 64 bit on the BW server side.
    - SNC0: p:service.test.bobj at DOMAIN
    - SU01 --> BO_Service ; SNC: p:service.test.bobj at DOMAIN
    - Entitlement system tab --> username: BO_Service
    SNC Name: p:service.test.bobj at DOMAIN
    - SNC settings tab:
    SNC Lib: c:\winnt\gsskrb5.dll
    Mutual Authentication settings: p:SAPServiceBP0 at DOMAIN
    In CMC, the role can be imported if "RFC activated" option unchecked in SNC0.
    I found a few threads on the same topic, but they are all not answered:
    SNC Client side configuration error
    SNC Configuration Error: Incomplete logon Data
    Can you please provide details of the solution if you have impleted a same scenario successsfully, or any thoughts to help the investigation?
    Thanks in advance!
    Regards,
    Jonathan

    Hi Ingo,
    Sorry for taking so long to reply, we are trying to set up server side trust and enable SSO; but we still couldn't success.
    What we did is:
    1. We followed installation guide chapter 6, generate certificate and PSE, etc. All looks good.
    2. Then we still have the "incomplete logon data" error when refreshing webi report after logon using Windows AD user ID.
    3. Then we trace the PFC connection, the log is as below. We checked several BO notes, e.g. 1500150, 1461247.. The part bothers us is that we even don't have URI displayed in the log when system trying to use SNC, and we couldn't get more info on this which make us very difficult to diagnosis.
    Can you please help? Thanks a lot!
    Thu Mar 31 10:54:46.857 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Authentication model for SAP connectivity is SSO
    Thu Mar 31 10:54:46.857 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Determining if we can connect using SNC. Calling CanAuthenticate...
    Thu Mar 31 10:54:46.919 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Unable to authenticate using SNC because the URI does not meet the minimum connection requirements.
    Thu Mar 31 10:54:46.919 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Determining if we can connect using SSO. Calling CanAuthenticate...
    Thu Mar 31 10:54:46.919 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Authentication model for SAP connectivity is SSO
    Thu Mar 31 10:54:47.013 ThreadID<1980> SAPMODULE : SAPAuthenticationService: The SAP SSO authentication process will fail because the SAP secondary credential are not properly updated and the password is blank.
    Thu Mar 31 10:54:47.013 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Trying to connect to SAP using this URI : occa:sap://;PROVIDER=sapbw_bapi,R3NAME=PB0,GROUP=BI_Group1,MSHOST=sapaupdb04,LANG=en,CLIENT=100,CATALOG="ZSPUM602",CUBE="ZSPUM602/ZSPUM602_Q50"
    Thu Mar 31 10:54:47.013 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Calling m_pRfcWrapper->RfcOpenEx() ...
    Thu Mar 31 10:54:47.154 ThreadID<1980> SAPMODULE : SAPAuthenticationService: RfcOpenEx(...) returned 0
    Thu Mar 31 10:54:47.154 ThreadID<1980> SAPMODULE : SAPAuthenticationService: Call to m_pRfcWrapper->RfcOpenEx() took 0.141 seconds
    Thu Mar 31 10:54:47.154 ThreadID<1980> SAPMODULE : SAPAuthenticationService: SAPAuthenticationService::~SAPAuthenticationService

  • Error when refreshing web intelligence document less then every minute

    Hi all,
    I get the following error, when refreshing document via javascript more often then every minute:
    Server Error in '/Dashboard' Application.
    FatalException occured. The cause was : BusinessObjects.Enterprise.OcaFramework.Oca.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2 at BusinessObjects.Enterprise.OcaFramework.ManagedService.invoke(MethodInfo method, Object[] args, IDictionary context)
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
    Exception Details: BusinessObjects.Enterprise.OcaFramework.ManagedServiceFatalException: FatalException occured. The cause was : BusinessObjects.Enterprise.OcaFramework.Oca.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2 at BusinessObjects.Enterprise.OcaFramework.ManagedService.invoke(MethodInfo method, Object[] args, IDictionary context)
    Source Error:
    Line 121:               
    Line 122:                    //Session["StorageToken" + strDocId] = doc.StorageToken;
    Line 123:               doc = reportEngine.OpenDocument(intDocID);
    Line 124:               //doc = reportEngine.GetDocumentFromStorageToken(storageToken);
    Line 125:               doc.Refresh();
    Source File: c:\inetpub\wwwroot\dashboard\document.aspx.cs    Line: 123
    Stack Trace:
    [ManagedServiceFatalException: FatalException occured. The cause was : BusinessObjects.Enterprise.OcaFramework.Oca.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
       at BusinessObjects.Enterprise.OcaFramework.ManagedService.invoke(MethodInfo method, Object[] args, IDictionary context)]
       BusinessObjects.ReportEngine.WI.Internal.Server.OCCA._WICDZProxy.initInstance(Byte[] p0, UTF8StringHolder p1)
       BusinessObjects.ReportEngine.WI.Internal.Server.OCCA.OCCAServerStub.InitInstance(String clientInfo, Int32& returnCode)
    [CommunicationException: The Web Intelligence server could not be reached. Contact your Business Objects administrator. (Error: RWI 00236)]
       BusinessObjects.ReportEngine.WI.Internal.Server.OCCA.OCCAServerStub.InitInstance(String clientInfo, Int32& returnCode)
       BusinessObjects.ReportEngine.WI.Internal.Server.ServerCaller.InitInstance(String clientInfo)
       BusinessObjects.ReportEngine.WI.Internal.WIDocumentInstance..ctor(WIReportEngine engine, Int32 documentId)
       BusinessObjects.ReportEngine.WI.Internal.WIReportEngine.OpenDocument(Int32 documentId)
       Dashboard.document.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\dashboard\document.aspx.cs:123
       System.Web.UI.Control.OnLoad(EventArgs e)
       System.Web.UI.Control.LoadRecursive()
       System.Web.UI.Page.ProcessRequestMain()
    Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407
    I searched forum and google for this error, but I didn't find anything. Did you heard of this error? How can I fix it?
    My BO Version is BusinessObjects Enterprise XI (without any ServicePacks). Is there a SP which fix this error?
    Thank you for every idea!!!

    Hi,
    Copy File from Client system to server in same folder location .
    Make sure in Edit Query option Editable & Refreshable options are checked .
    Please check the links below  .
    Webi Excel Personal Data Provider Dynamic Data
    How to create a webi report using excel as source
    Excel as datasource in Infoview
    Excel source located in Infoview

  • Error when refreshing workbook in BEx: Specific Macro CallBack not found

    One of our users is getting the following error when refreshing any BEx workbook (in BI7):
    Problems while calling the exit on refresh: Specified Macro 'CallBack' is not found in the workbook
    This error suddenly started this week, everything was fine before that, and no changes have been made to the user's PC. The problem is specific to this one user's PC.
    Any ideas?
    -Jason

    Hi,
    It seems a common error.
    There is a note that mentions the error, and was fixed since BI addons SP 8
    Note: 1267942 -  Custom macro not being executed on a workbook
    Download and test the latest version: bi710sp12_1200-10004472.exe
    This should fix the issue.
    FYI: SAPGUI 640 is not supported by SAP since 2008. If you are using this version, please download the SAPGUI 7.10 as well.
    Thanks
    Edward John

  • Get AccessControlException(access denied) when refresh page

    Our applet have AccessControlException when refresh the ie browser but the first time open no such a problem! And when we use other host which use a different proxy no such a problem either. Don't know why , is it the problem of proxy?
    any idea ? many thanks!
    here is the log:
    INFO - Wed Jan 16 16:09:30 EST 2008: getResponseTime Debug1-- openConnection time: 0ms
    network: Connecting https://hostname/_en.html with proxy=HTTP @ proxyname:8080
    network: Connecting https://hostname/_en.html with cookie "BCSI-CSA1021104=2"
    INFO - Wed Jan 16 16:09:34 EST 2008: getResponseTime Debug3-- getInputStream time: 4500ms
    liveconnect: Invoking JS method: ua
    INFO - Wed Jan 16 16:09:34 EST 2008: Log page URL -- https://hostname/result.html?timestamp=Wed Jan 16 16:09:34 EST 2008&ip=''&jvm=Sun Microsystems Inc.,1.5.0_14&os=Windows XP,5.1&echo_time=4500ms&UserAgent=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
    INFO - Wed Jan 16 16:09:34 EST 2008: logUsrInfo Debug5-- openConnection time: 0ms
    INFO - Wed Jan 16 16:09:34 EST 2008: JVM version checking passed!
    +(the first time open page can pass!)+
    liveconnect: Invoking JS method: showApplication
    basic: Stopping applet ...
    basic: Finding information ...
    basic: Releasing classloader: sun.plugin.ClassLoaderInfo@134e4fb, refcount=0
    basic: Caching classloader: sun.plugin.ClassLoaderInfo@134e4fb
    basic: Current classloader cache size: 1
    basic: Done ...
    basic: Removed progress listener: sun.plugin.util.GrayBoxPainter@1be0f0a
    basic: Joining applet thread ...
    basic: Destroying applet ...
    basic: Disposing applet ...
    basic: Joined applet thread ...
    basic: Unregistered modality listener
    basic: Quiting applet ...
    basic: Registered modality listener
    liveconnect: Invoking JS method: document
    liveconnect: Invoking JS method: URL
    basic: Referencing classloader: sun.plugin.ClassLoaderInfo@134e4fb, refcount=1
    basic: Added progress listener: sun.plugin.util.GrayBoxPainter@50988
    basic: Loading applet ...
    basic: Initializing applet ...
    basic: Starting applet ...
    basic: Referencing classloader: sun.plugin.ClassLoaderInfo@134e4fb, refcount=2
    basic: Releasing classloader: sun.plugin.ClassLoaderInfo@134e4fb, refcount=1
    INFO - Wed Jan 16 16:09:44 EST 2008: getResponseTime Debug1-- openConnection time: 0ms
    network: Connecting https://hostname/fx-canada/login_detail_fr-ca.html with proxy=HTTP @ proxyname/
    network: Server https://hostname/fx-canada/login_detail_fr-ca.html requesting to set-cookie with "BCSI-CSA1021104=2; Path=/"
    INFO - Wed Jan 16 16:09:48 EST 2008: getResponseTime Debug4-- throw exception time: 4515ms
    WARN - Wed Jan 16 16:09:48 EST 2008: Cannot get system response time!
    java.security.AccessControlException: access denied (java.net.SocketPermission hostname:8080 connect,resolve)
    at java.security.AccessControlContext.checkPermission(Unknown Source)
    at java.security.AccessController.checkPermission(Unknown Source)
    at java.lang.SecurityManager.checkPermission(Unknown Source)
    at java.lang.SecurityManager.checkConnect(Unknown Source)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.proxiedConnect(Unknown Source)

    The security credentials for a JMS "send" operation are not taken from the username and password that you pass to the "createConnection" method, but from the security login context in effect when you call "send". So, if you want this to happen using a particular security context, you need to make sure that you have set this up before you make the call.
              There are a number of ways to do this in WLS. Your best bet would be to check the security documentation, or do ask on the security newsgroup for the best way to do this in 8.1.

  • Which BO-account is used when refreshing a metric?

    Hello,
    I have made a metric with BO-application dashboard manager. The metric is stored in table ci_probe and when I execute the stored excutable sql I get data back.
    Now I want to load the data in the performance management database when refreshing a metric.
    I don't get any data in the tabel ci_probe_value.
    I made a trace with SQL-profiler to see if my account reaches the database. It doesn't.
    I have changed the DBUSER field for my account and the Administrator and the PMUser account. They all have the same value and this account has sysadm rights on the database.
    It didn't help.
    When I refresh a metric which account is used the read the data from the database.
    Please advise,
    Thanks
    Joek Poort

    Hi Joek,
    PMUser is used mainly for the DM & PM system to access resources.
    When it comes to data, the connection used in the universe is used to access the database. If you can create a webi report using your universe in question you should be able to see if you get back data or not.
    I think your problem could also maybe be with the definition of the metric in the universe. Test it by simply just droping the metric into webi and check the SQL that is generated.
    Check the BEGIN_DATE and END_DATE of the @prompt (or sometimes BEGIN_DT and END_DT) syntax.
    Regards
    Jacques

  • Timeout when calling long running Oracle Apps Adapter API calls

    When making a Oracle Apps Based adapter from ESB, Transactions are getting timedout for running calls (~ > 5 mins)
    1) Created a Oracle Apps Adapter to execute a API call that returns, in our case, customer data.
    2) Created a BPEL Which invokes this API based Adapter via. a partner link.
    3) Following errors for calls which take ~ >5, transaction is timeout, when invoked from BPEL/ESB/SOAP UI Client.
    From domain.log
    ==========
    <2009-04-21 18:54:25,718> <DEBUG> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
    org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: Timed out
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.populateFaultMessage(WSIFOperation_JaxRpc.java:3086)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1728)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1473)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1196)
         at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:476)
         at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:436)
         at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:790)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:395)
         at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
         at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3715)
         at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1655)
         at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:317)
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5710)
         at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1085)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:132)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:161)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
         at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at CubeEngineBean_LocalProxy_4bin6i8.syncCreateAndInvoke(Unknown Source)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:515)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:457)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:131)
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
         at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
         at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
         at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
         at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
         at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
         at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
         at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
         at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.xml.rpc.soap.SOAPFaultException: Timed out
         at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:568)
         at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
         at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
         at oracle.j2ee.ws.client.dii.CallInvokerImpl.directInvoke(CallInvokerImpl.java:726)
         at oracle.j2ee.ws.client.dii.BasicCall.directInvoke(BasicCall.java:743)
         at oracle.j2ee.ws.client.dii.BasicCall.invoke(BasicCall.java:649)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1714)
         ... 83 more
    <2009-04-21 18:54:25,721> <ERROR> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened: exception during SOAP invoke: Timed out; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: Timed out
    <2009-04-21 18:54:25,752> <DEBUG> <yeruvp.collaxa.cube.engine> AJPRequestHandler-RMICallHandler-61, a4 <invoke> partner OrgCustAdapter_pl, wikey:7990001-BpInv0-BpSeq0.3-3, bpel code line:84, Connection info:oracle_jdbc_driver_T4CConnection_Proxy@17f3851, connection hashCode:25114705, autocommit:false, Transaction info:[Transaction : orabpel : Xid( Global Id 1b.16.00.7d.00.00.00.00.2f.d3.6d.ca.20.01.00.00.17.41.03.00.00.00.00.00, Format Id 1330790740)], jtaTxState:1, CubeInstance:7990001, Process name:testCustomer_BPEL
    Now looking to troubleshoot this Timed out issue.
    i, Does this need to increase any configuration file timeout parameter on EBS Adapter or other component ?
    Any suggessions to fix/towards resolution is appricated.
    Thanks,
    sgaraga

    After increasing sync-time-out and global transaction time out to 1800. Issue is still reported.
    We are not using the jdbc pool.
    Still not sure what we are missing here and running into this:
    WSIFInvocationHandler::invoke> invoke failed
    org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested
    exception is:
    javax.xml.rpc.soap.SOAPFaultException: Timed out
    In addition:
    ========
    Tested calling this PL/SQL API (exactly the same API CALLED in BPEL) in TOAD and this ran for 20 mts in DB.
    With the changes(sync-time-out,global transaction time,hpptd.conf, and transaction-manager.xml ) in SOA configuration then we are getting the exception ..
    So, we need help with SOA configuration to get the BPEL service working when the API called within BPEL service is taking approximately 20 mts.
    Edited by: sgaraga on Apr 22, 2009 4:29 PM

  • Timeout when calling Oracle Apps Adapter API calls.

    1) Create a Oracle Apps Adapter to execute a API call that returns, in our case, customer data.
    2) Create a BPEL Which invokes this API based Adapter via. a partner link.
    Observations:
    A) Posts the following errors for calls which take ~ >5, transaction is timeout, when invoked from BPEL/ESB/SOAP UI Client.
    <2009-04-21 18:54:25,718> <DEBUG> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
    org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: Timed out
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.populateFaultMessage(WSIFOperation_JaxRpc.java:3086)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1728)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1473)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1196)
         at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:476)
         at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:436)
         at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:790)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:395)
         at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
         at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3715)
         at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1655)
         at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:317)
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5710)
         at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1085)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:132)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:161)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
         at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at CubeEngineBean_LocalProxy_4bin6i8.syncCreateAndInvoke(Unknown Source)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:515)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:457)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:131)
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
         at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
         at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
         at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
         at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
         at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
         at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
         at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
         at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.xml.rpc.soap.SOAPFaultException: Timed out
         at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:568)
         at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
         at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
         at oracle.j2ee.ws.client.dii.CallInvokerImpl.directInvoke(CallInvokerImpl.java:726)
         at oracle.j2ee.ws.client.dii.BasicCall.directInvoke(BasicCall.java:743)
         at oracle.j2ee.ws.client.dii.BasicCall.invoke(BasicCall.java:649)
         at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1714)
         ... 83 more
    <2009-04-21 18:54:25,721> <ERROR> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened: exception during SOAP invoke: Timed out; nested exception is:
         javax.xml.rpc.soap.SOAPFaultException: Timed out
    <2009-04-21 18:54:25,752> <DEBUG> <yeruvp.collaxa.cube.engine> AJPRequestHandler-RMICallHandler-61, a4 <invoke> partner OrgCustAdapter_pl, wikey:7990001-BpInv0-BpSeq0.3-3, bpel code line:84, Connection info:oracle_jdbc_driver_T4CConnection_Proxy@17f3851, connection hashCode:25114705, autocommit:false, Transaction info:[Transaction : orabpel : Xid( Global Id 1b.16.00.7d.00.00.00.00.2f.d3.6d.ca.20.01.00.00.17.41.03.00.00.00.00.00, Format Id 1330790740)], jtaTxState:1, CubeInstance:7990001, Process name:testCustomer_BPEL
    Now i am looking to troubleshoot this Timed out issue.
    i, Does this need to increase any configuration file timeout parameter on EBS Adapter or other component ?
    Any suggestions to fix/towards resolution is appreciated.
    Thanks,
    sgaraga

    After increasing sync-time-out and global transaction time out to 1800. Issue is still reported.
    We are not using the jdbc pool.
    Still not sure what we are missing here and running into this:
    WSIFInvocationHandler::invoke> invoke failed
    org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested
    exception is:
    javax.xml.rpc.soap.SOAPFaultException: Timed out
    In addition:
    ========
    Tested calling this PL/SQL API (exactly the same API CALLED in BPEL) in TOAD and this ran for 20 mts in DB.
    With the changes(sync-time-out,global transaction time,hpptd.conf, and transaction-manager.xml ) in SOA configuration then we are getting the exception ..
    So, we need help with SOA configuration to get the BPEL service working when the API called within BPEL service is taking approximately 20 mts.
    Edited by: sgaraga on Apr 22, 2009 4:29 PM

  • Ora-04045 when refreshing materialized view

    Can any one help with this error ora-04045 .I get this error when refreshing the materialized view for the first.second time when i refresh the materialized view it gets refreshed.
    My database version is 8.1.7.x

    Yes it is enabled.if you refresh for the 1 time it show object invalid when you refresh again it refreshes and object is valid.i am using dbms_refresh pacakge to do this.one more problem is that i have made a procedure in which i am calling dbms_refresh pakcage 8 times to refresh 8 views.if 1 gets refreshed then 2 will not it will fail.i don't understand this behaviour

  • Workbook when refreshed loosing formatting

    Hi All,
    We have a workbook when run giving data properly, but the same when refreshed loosing the formatting. i.e. the data is being displayed but the cells are not highlighted and colours of the cells not displayed etc.
    Please let me know if anyone faced similar issue and the solution.
    Thanks
    Hima Bindu

    Hi Veerendra,
    It Worked with small changes.
    I had to go to the design mode of the Workbook. Right click on the Analysis Grid-> Properties -> Check the box Apply Formatting
    and save the workbook.
    Thanks a lot.
    Hima Bindu

  • Group Tree issue when refreshing- Crystal for Visual Studio 2010 WPF Viewer

    Hello,
    We've run into an issue when refreshing reports with the WPF viewer for Visual Studio 2010. After the report is refreshed, the Group Tree is blank and it should have values. For example, you run a report and see values in the Group Tree. If you refresh the report with the same parameter values the Group Tree is blank.
    Has anyone run into this yet?
    Thanks,
    Tyler

    That is correct.
    I just did a quick test and was not able to reproduce the issue.
    Details of test:
    1) Create a new app;
    File | New | Project
    Visual Basic | reporting -> Crystal Reports WPF Application
    2) Add the "Open File" button to the viewer (ShowOpenFileButton off of the WPF viewer properties)
    3) Run app
    4) Browse to a report that has a number of groups >250
    5) Refresh report using the Refresh button on the viewer
    I'll work on this a bit later today, see if I can repro it another way. Meanwhile, can you provide mode details (code) on how you repro the issue?
    - Ludek

  • Invalid Year error when refreshing the report with date prompt

    Hi All,
    I am working on BO XI 3.1 with Informix database.
    When refreshing the report without any date prompt the report is running fine,but when applying the date prompt it is giving the error message
    "Invalid year in the date".
    I have tried changing the value in the advance tab of the object property to 'yyyy-mm-dd hh:mm:ss'
    But it also din't work for me.
    Please suggest.
    Thanks and Regards,
    Rishabh

    Hi Experts,
    Thanks for your suggestions.
    Since changing the PRM file was not a fesiable solution for us.
    We have manged to find a work around to solve this issue
    We have created the filters at universe level with following formula for all the date objects which we ere using at report level as a prompt:
    @Select(classname\objectname)=TO_DATE(@Prompt('Enter Date:','D',,mono,free,not_persistent), '%Y/%m/%d')
    Although when we parse this formula it wil give an error message saying 'illigle operation',
    still it will work when we use this at report level.
    Thanks and Regards,
    Rishabh

Maybe you are looking for