Synchronous Transient Process Shows "500 Internal Server Error" Instead of Timeout on HTTP Post (Doc ID 864557.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.3 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Apr-2011***


Symptoms

When a partner link with a long running HTTP Post is invoked from a synchronous transient BPEL
process, the process does not conform to any timeout settings.

While the partner link takes longer than the timeout values, there is no timeout in the log and the
instance does not show up in the console. A 500 Internal Server Error is shown in the Console
initiation window after a few minutes.

When the partner link eventually returns, the logs indicate that the instance cannot be found and
ORABPEL-02182 and ORABPEL-02094 are shown in the logs.
There is still no instance information in the Console.

-- Steps To Reproduce:
1. Run a simple servlet which returns an HTTP Post. Build a wait time in the servlet that is
longer than your timeout values as defined in domain.xml, orion-ejb-jar.xml and transaction-manager.xml.
2. Create a BPEL process which calls the servlet.
3. Initiate the process.

Generally the timeouts are defined in the following files:
<SOA_Home>\bpel\domains\<domain_name>\config\domain.xml**
<SOA_Home>\j2ee\<home>\application-deployments\orabpel\ejb_ob_engine\orion-ejb-jar.xml
<SOA_Home>\j2ee\<home>\config\transaction-manager.xml
**synchMaxWaitTime can be modified in your BPEL Console as well.

Timeouts should be defined such that the synchMaxWaitTime in domain.xml is less than the transaction timeout values in orion-ejb-jar.xml and those values should be less than the timeout value in transaction-manager.xml.






Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms