An Error Thrown From PLSQL is not Handled in BPEL and Causes the Process to End
(Doc ID 456481.1)
Last updated on MARCH 30, 2019
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 and later
Information in this document applies to any platform.
This problem can occur on any platform.
On 10.1.3.1.0 when using the DB Adapter to call a stored procedure in the database, when an error is thrown from the stored procedure, the error is logged in the BPEL log file, but the process does not complete. It looks like the server is rolling back the transaction and does not complete its processing.
No faulted BPEL instance appears on failure, remote exceptions are not handled by the BPEL process anymore, and exceptions are misclassified as retriable/not retriable.
-- Steps To Reproduce:
1. Create and validate a stored procedure.
2. Create a BPEL process which calls the stored procedure through a DB Adapter.
3. Deploy and initiate the process while forcing the stored procedure to fail (disconnect, etc).
4. View the BPEL process in the BPEL Console and see that no faulted BPEL instance appears on failure, remote exceptions
are not handled by the BPEL process anymore, and exceptions are misclassified as retriable/not retriable.
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