BPEL Instances Stuck in Running, but Never Complete, 'com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null.'
(Doc ID 1292463.1)
Last updated on JANUARY 03, 2020
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.3.3 to 10.1.3.5.0
Information in this document applies to any platform.
***Checked for relevance on 12-May-2014***
You are running BPEL processes in 10g. It is noticed that there are in-process BPEL instances, but these never complete either successfully or with a failure, they just remain in-flight. This will be seen usually when there are a large number of instances submitted over a short span of time.
The following error is seen in the container logfile in $OH/opmn/logs/<BPEL container>.log, notice that the collaxa.cube.engine.delivery logger is set to DEBUG:
You may have already extended the following timers to long expiration times, but still receive the ReceiveTimeOut error:
(1) $OH/Apache/Apache/conf/httpd.conf --> Timeout
(2) Log into the BPEL console for the domain or domains in question http://<hostname>:<port>/BPELConsole -> syncMaxWaitTime .
(3) $OH/j2ee/<BPEL Container, e.g. oc4j_soa>/config/transaction-manager.xml -> transaction-timeout
(4) $OH/application-deployments/orabpel/ejb_ob_engine/orion-ejb-jar.xml -> all transaction-timeout values
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document