Transaction timed out after 300 seconds when invoking synchronous WS
roheieAug 18 2010 — edited Feb 27 2020Platform: Jdev and SOA suite 11.1.1.3 on Windows
I have created a simple composite with a BPEL process that invokes two synchronous external web services in sequence. The services are both Warehouse Builder jobs that take about 30 mins to complete and the first needs to successfully complete before the second is started. When I try to run this it fails with
<Error> <oracle.soa.bpel.engine.dispatch> <BEA-000000> <<BaseDispatchTask::logHandleMessageError> Failed to handle dispatch message... exception ORABPEL-05002
Message handle error. error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
I have verified that the BPEL process completes successfully if I tweak the services to complete in less than 300 seconds.
I have tried to increase the timeout by doing the following:
- In JDeveloper increase oracle.webservices.httpReadTimeout
- In Weblogic EM I have increased syncMaxWaitTime from "SOA Administration -> BPEL Properties"
- In weblogic console I have increased the timeout of the MBean "soa-infra" under deployment
- The timeout of JTA has been increased
Still the problem persists, and I am at a loss as to what I should try next. I have a feeling I have missed something somewhere... Any ideas?
Thanks,
Roald