Last updated on NOVEMBER 21, 2016
Applies to:Oracle Business Process Management Suite - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
An asynchronous BPM process calls a synchronous service via SOAP. The service transforms its input data via a sequential mediator which in turn executes a PLSQL stored procedure via a DBAadapter.
BPM -> WebService -> SOA -> Mediator (sequential) -> DBAadapter -> PLSQL (stored procedure)
When a Transaction Time-out occurs when calling the PLSQL, results in a faulted DBAadapter and Mediator but it does not return a fault to the BPM process. This means that the BPM process sits in a status awaiting a response that it will never get as the SOA service has competed with a fault. Thus in the EM we see the process status as running and the Mediator service as faulted and neither of them can be retried. Thus this instance remains in the same state and there is no way to move the instance forward from the EM.
However this is happening only with the timeouts. We have found that the other genuine faults (such as connection failures and package compilation failures) are returned from the db are in fact returned to the BPM process
Thus, it is only for Transaction Time-out that this behaviour occurs where by the calling BPM instance is running and the Mediator is faulted.
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