Prior to SBM 11.0, the SBM Orchestration Engine used JBPM for the BPEL engine. Under JBPM, synchronous orchestrations that took longer than 60 seconds to complete were timed out by Application Engine, but the orchestration would continue running. For asynchronous orchestrations, there was no particular timeout.
However if you are running synchronous orchestrations the AE webservice timout setting affects all web service calls from AE including synchronous orchestration workflows. The default value for this is 30 seconds and it can be changed in the system administrator under Options>settings>database>Web Service Invocation Timeout
NOTE: The default Orchestration Engine timeout is disabled beginning in SBM 10.1.5, so these steps are no longer necessary in newer versions. Change the Application Engine timeout as explained above.
SBM 10.x database upgrade to SBM 11.x gives error "Failed to upgrade Orchestration Engine database. Connection to the Application Engine server has timed out."
SOAP Fault String: addDeployUnitsTo RP: RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response The orchestration fails with error: SOAP Fault String: RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response
