SOA Composite Timing Out When Running In Cluster With Unable To Invoke Endpoint URI

(Doc ID 2325465.1)

Last updated on NOVEMBER 13, 2017

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

Below are symptoms of issue

-SOA composite SOMSalesOrderMessageRouter further invokes SOMSalesOrder.
- observing that these composites are failing with timeout errors, when we run SOA in cluster mode i.e. when both nodes of SOA are up and running
- The issue doesn't occurs when only 1 [either of the 2] node is running


ERROR
-----------------------
com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=Waiting for response has timed out. The conversation id is urn:50A8E450890F11E7BF7D497D5C4325A9. Please check the process instance for detail.
,detail=Waiting for response has timed out. The conversation id is urn:50A8E450890F11E7BF7D497D5C4325A9. Please check the process instance for detail.
,code=0}




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