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

Similar Messages

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

Capturing error messages from Oracle EBS APIs when using Oracle Apps Adapter

We are using Oracle applications adapter to call Oracle EBS (both R11.5 and R12) APIs. I want to understand the best practice around error handling when using Oracle Apps Adapter to call Oracle EBS.
Here are some observations:
1. Most of the APIs return X_RETURN_STATUS and X_MSG_DATA containing the status and messages if any.
2. If the MSG COUNT is 1 then X_MSG_DATA contains the message, if MSG COUNT is > 1. X_MSG_DATA is empty.
We know that when calling the API directly from PL/SQL, we need to loop through FND_MSG_PUB to fetch all messages when there are more than 1. How do we achieve the same using Apps Adapter as Apps Adapter generates the PL/SQL block to call the API dynamically at runtime.
In some APIs, which have table/rec types as input or output parameters, Apps Adapter generates a wrapper package to do conversion from SQL--> PL/SQL and viceversa. In this case the adapter calls the custom package generated which internally calls the API. For these APIs we were able to put the logic to loop through FND_MSG_PUB and return a concatenated string as value of X_MSG_DATA.
But what should we do for the APIs which do NOT have a rec/table type as input or output, in which case the Apps Adapter directly calls the API and there is no intermediate custom package?
How are others handling this?

Please see the section "Handling Functional Errors" in the below link
Oracle Fusion Middleware Adapter for Oracle Applications User's Guide

Binding Error while calling Oracle Apps Adapter

Hi,
I have configured an oracle apps adapter to be called from the a BPEL Process in Jdev. The operation is to insert data in an oracle interface table.
I m getting the following error when the BPEL process is invoked from Console. Please suggest where could be the problem.
<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>null
</code>
</part>
-<part name="summary">
<summary>
file:/C:/SOA/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_BPELProcess1_2.0_70717543df91cf3e80346845ccf64937.tmp/OraAppAdp.wsdl [ OraAppAdp_ptt::insert(RaCustomersInterfaceAllCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception.
insert failed. Descriptor name: [OraAppAdp.RaCustomersInterfaceAll].
; nested exception is:
ORABPEL-11616
DBWriteInteractionSpec Execute Failed Exception.
insert failed. Descriptor name: [OraAppAdp.RaCustomersInterfaceAll].
Caused by java.lang.NullPointerException.
</summary>
</part>
-<part name="detail">
<detail>null
</detail>
</part>
</bindingFault>
I have checked the oc4j-ra.xml , data-sources.xml and the connection factory on the enterprice manager.
Thanks
varun

Hi all,
i have exactly the same error and use the same applications and adapters.
i don't know what's wrong.
i thing the connection pool can open the connection to the database, but cannot write anythin in the database. maybe the Table cannot be found, but it's only a guess.
Any other idea or maybe a solution?
regrads

(BUG?) Oracle Apps Adapter - Unable to setup Concurrent with no parameter

Hi all.
I'm facing a problem when using Oracle Apps Adapter 10.1.3.1
In JDev Adapter Configuration Module Browser, when I want to configure it to execute a concurrent program that has no input parameter, the Module Browser does not work (the OK button does nothing)
Examples of concurrent with no parameters are:
1) Discrete Manufacturing->Inventory->Material Transaction->Open Interfaces->Inventory Transaction Open Interface->Concurrent Programs->Material Transactions Interface Manager (This one is the main issue I'm facing)
2) Supply Chain Management->Shop Floor Management->Lot Based Job->Open Interfaces->Lot Based Job Open Interface->Concurrent Programs->Manager: Lot Move Transactions
Other concurrents that have parameters all seems to pass in the configuration wizard.
Does any one know about this issue?
Thanks.
Denis

We've already been in conversation with the AppsAdapter developers about this.
Part of the problem is that you have to have NLS_LANG set correctly on your PC. So if the NLS_LANG on your Apps install is US then the PC needs to be set like this also.
I have some documentation which I can forward if you send me your contact details to [email protected]
Not saying that this will solve all your problems, as we found a few with this adapter but hopefully will put you on the right track.

CSD_RULE_MATCH_FAILED-calling service request api from oracle apps adapter

We are doing integration between Siebel and Oracle Apps. When a service request is created on Siebel we are passing that in Oracle Apps using Oracle Apps adapter which is calling a custom API which is doing all the validations and in turn is calling a public api for service request creation. There are two types of service requests - Field Service and Depot Repair. For Field Service we are able to successfully insert the data on Oracle Apps, but for Depot Repair we are getting an error 'CSD CSD_RULE_MATCH_FAILED' from the standard API.
We have checked the setup and found it is proper. We invoked the pl/sql API from sql developer and we are able to insert the data. So we are facing this issue only when calling the api from oracle apps adapter.
In the invoke call we have set these properties -
jca.apps.RespApplication
jca.apps.Responsibility
jca.apps.Username
Based on our analysis till now it is looking like a security context setup issue, but we are not really sure what properties to set.
Any help in getting this through will be greatly appreciated.
Thanks,
Shantanu

Hi Vijay,
We have created the apps adapter with default settings as 'apps' user and set the properties Responsibility, RespApplication, Username of <invoke>. Other than that no other settings has been changed.
Are we missing anything?
This adapter is able to hit the database in case of 'Field Service' but it is failing for 'Depot Repair'.
Edited by: 927382 on Apr 13, 2012 2:19 AM

Apps Adapter API is called before Db Adapter inserting data

Hi All,
I am using a bpel process which calls db adapter to insert/update data in staging table, after this activity i am calling a Apps Adapter PLSQL API where it takes the data from staging table and performs some functionality. But the problem here is Apps adapter PlSQL API is getting called before isnerting data in staging table.
Below are the steps in BPEL Process,
1. receive activity
2. data transformation
3. invokes db adapter through merge operation to insert/update in staging tables
4. invoke Apps Adapter PLSQL API
Error is thrown at Apps Adapter invoke activity, saying null values. presently we used a wait activity before invoking apps adapter.
Do the invoke of Apps Adapeter doesnt happen after Db Adapter inserting data?
Thanks,
Ra

Hi Team,
Even I faced the same problem.
I am checking, do we have any configuration setting to avaoid these kind of problem.
Even my process has point 2 & 3 in a single sequence and point 4 in another sequence.
Any help to resolve this problem is greatly appreciated.
Thanks for your help in adavance.
Cheers
Chandru

Can we call and execute a request set using db adapter or oracle apps adapt

Hi,
Can we call and execute a request set(which executes a set of packages in a sequence) using db adapter or oracle apps adapter similar to calling a stored procedure and concurrent program?
thanks,
RV

1) In BPEL call the DBAdapter in a sequence, make sure you set the partnerlink 'property' to transaction=participate.
2) Or create a package that calls the other packages in a sequence
Marc
http://orasoa.blogspot.com

Unable to create Oracle Apps Adapter whose API parameters are Records

Hi All,
I face an issue in creating an Apps adapter whose API parameter's are of type Records. From previous posts I came to know that its one of the bug in JPublisher.
I'm new to this term. Can you please provide how to create this adapter?
Exception raised: The Wrapper procedure could not be found in the package for the schema.
Thanks
Karthick

where are you getting this error ? Sometimes some API's cannot be called from Oracle Apps Adapter, will be getting some JPublisher Error, try configuring the same API from Database Adapter, this workaround works sometimes....
If you get the error in a different instance while it was working in earlier instance, read further...
Generally when you are working with the oracle apps adapter, and for any API, the input paramaters are record types, there will be a wrapper package created for the API you have configured. So, this error comes when you migrate the composite to a different instance, make sure you have moved that wrapper package also to the new database instance, if you do that, this error will go.
Hope this helps,
N

Re:Oracle Apps Adapter and invocation of Process_order API

Hi,
I am trying to create sales order in Oracle Apps 11.5.10.2 using Oracle Apps Adapter by invoking Process_order API and facing the following problem.
file:/D:/SOA_SUITE/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_EDI850InboundService_1.0_973a35abc5c4e4b30f414886437b790d.tmp/writeEDIData
2OracleService.wsdl [
writeEDIData2OracleService_ptt::writeEDIData2OracleService(InputParameters,Outpu
tParameters) ] - WSIF JCA Execute of operation 'writeEDIData2OracleService'
failed due to: Error while converting to a Java struct object.
Unable to convert the XSD element P_HEADER_REC whose user defined type is
OE_ORDER_PUB_HEADER_REC_TYPE. Cause: java.sql.SQLException: Closed Connection
[Caused by: Closed Connection]
; nested exception is:
ORABPEL-11802
Error while converting to a Java struct object.
Unable to convert the XSD element P_HEADER_REC whose user defined type is OE_ORDER_PUB_HEADER_REC_TYPE. Cause:
java.sql.SQLException: Closed Connection [Caused by: Closed Connection]
Check to ensure that the XML data describing the user defined type matches the
definition of the struct in the XSD. Contact oracle support if error is not
fixable.
I am using SOA-Suite 10.1.3.3.0.
Can someone help me on this.
Regards
Lalit

Hi lalit,
Upgrade your database 10.0.2 to 10.1.0.5.
You can apply the Oracle Database 10g release 10.1.0.5 patch set to the following Oracle Database 10g releases (10.1.0.2, 10.1.0.3, or 10.1.0.4) installations.
See document 263719.1 on the OracleMetalink Web site:
To locate document 263719.1:
-->Log on to OracleMetalink.
-->Click Advanced at the top of the OracleMetalink page.
-->Enter 263719.1 in the Document ID field, then click Submit.
Cheers,
Abhi...

Oracle Apps adapter: User name issue

Hi All,
I am using SOA 11g to call an API in EBS using Oracle Apps Adapter .I am passing User name,Responsibility Name and other parameteres in invoke properties. Now the API is called successfully with most of the user names while for few usenames it's not able able to resolve user id based on user name. Although if the API is called from Oracle Apps/PL SQL ,it is working for all the users.
Please suggest.
Thanks in advance

At what stage are you seeing this error?

Error - Oracle Apps Adapter

Hi,
I am getting the following error when I invoke oracle Apps Adapter.
The same working pretty well in DEV and when we moved the code to SIT its behaving this way.
Another issue is even though in the flow trace, it says faulted, but I can still see the record in the db and on top it adds as many duplicate records as no of faults in the flow trace.
<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'invoke_ar_inbound_st_proc' failed due to: DBWriteInteractionSpec Execute Failed Exception. unknown failed. Descriptor name: [unknown]. Caused by java.sql.SQLException: Cannot call Connection.commit in distributed transaction. Transaction Manager will commit the resource manager when the distributed transaction is committed.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part name="detail">
<detail>Cannot call Connection.commit in distributed transaction. Transaction Manager will commit the resource manager when the distributed transaction is committed.</detail>
</part>
<part name="code">
<code>0</code>
</part>
</remoteFault>
</bpelFault>
</fault>
___________________________________________________________________

Either remove the hard commit statements from your PL/SQL procedure/package or use non-XA data-source.
Regards,
Anuj

Business Event ORACLE.APPS.PER.API.ASSIGNMENT.UPDATE_EMP_ASG_CRITERIA

Hi,
According to Document id 1402385.1 , I have subscribed the business event ORACLE.APPS.PER.API.ASSIGNMENT.UPDATE_EMP_ASG_CRITERIA with a synchronous subscription with a phase 99. It is calling an extension which in turn calling hr_assignment_api.update_emp_asg api to update assignment details. Now it is working fine in Oracle forms.
But when the same operation is being done in SSHR Pages for Manager Self Service responsibility the process could not be completed due to the following error.
" The HR object is invalid Cause: The HR object which is attempted to be locked is inconsistent with the corresponding object in the HR Schema. Action: Retry the action with the correct object version number. " As the SSHR page do validation in P_VALIDATE= TRUE mode so this error is occurring.
Now i tried to analyse the XML file generated by the business event. But I am not able to find whether it is being called as P_VALIDATE = TRUE or FALSE I want to know how to check whether the business event is called in TRUE mode or FALSE mode.
Regards,
Rakesh

Hi ,
Thanks Vignes for your reply.
The problem is that I am trying to call a custom function through this business event which in turn is calling HR_ASSIGNMENT_API.UPDATE_EMP_ASG.
Now when I am changing job or position in SSHR page it is validating the data I entered. So while validating they call that business event too. Now entering into that custom function it cannot decide whether the API should be called in P_VALIDATE=FALSE mode or P_VALIDATE=TRUE mode.
So I am trying to know whether is there any way to know P_VALIDATE mode when the business event is fired.
Regards,
Rakesh

When to use Apps adapter and DB adapter?

Hi All,
For invoking a PL/SQL API(either a custom or System API) in Oracle Applications from BPEL Process which is better to use?When to use Apps adapter and DB adapter?
Thanks,
ChitraDevi

As Sen correctly states for the DB adapter you have to set the context manually using the fun_global.apps_initilize or Fnd_Client_Info.SET_ORG_CONTEXT. This is usually done in a wrapper procedure.
I wouldn't say I'm an expert in this field as I have only used the APPS adapter for 11.5.10. I believe things have changed a bit for R12, but from my experience with APPS, things change very slow so although R12 is 10g App Server I'm sure the principles are the same.
Sen is also correct saying that base tables are not accessible via the APPS adapter. Basically the apps adapter is there to expose services, base tables are not services.
My recommendation would be different based on the experience of the developer(s). The APPS adapter simplifies the development but may not have the flexibility. The apps adapters sweet spot is those services that are difficult to integrate with, e.g. business services, xml gateway. If these are used heavily I would use the APPS adapter.
What I personally do, even if I'm not using APPS, if I'm connecting to the database I will implement a function, stored procedure, or AQ. It is a little more hassle during deployment, but it treats it more like a service and you are not impacted if the tables change. This is not an endorsement for you to go down this path because it does have a requirement to have PL/SQL knowledge, and it breaks the notion of service abstraction from the DB.
cheers
James

Error while running BPEL Process with Oracle Apps Adapter.

Hi All,
I am trying to configure the oracle apps adapter in JDeveloper.
Here my EBS is running on different database where as SOA is installed on different database.
I am able to properly configure the adapter & deploy the process to weblogic server.
But when I am trying to run the process I am getting following errorr.
<p>
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510\nJCA Resource Adapter location error.\nUnable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/>\nThe JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='*<JNDI Name passed in Oracle apps Adapter.>*'.\nThe reason for this is most likely that either \n 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or \n 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to <JNDI Name passed in Oracle apps Adapter.>
</p>
Please suggest the solution for the same.
its really urgent . waiting for reply.
Edited by: aumathe on Dec 16, 2010 2:33 PM

Have you created a connection pool with the JNDI specified while configuring adapter in Oracle Apps adapter on weblogic admin console. You should create it at Deployments --> OracleAppsAdapter --> Configuration--> Outbound Connection pools
Make sure to update the adapter after creating a connection pool so that changes can take effect.
Regards,
Anuj

Timeout when calling Oracle Apps Adapter API calls.

Similar Messages

Maybe you are looking for