Understanding BPEL Global Transaction and Adapter Local Transaction Issues
(Doc ID 1344004.1)
Last updated on MARCH 30, 2019
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1]
Information in this document applies to any platform.
BPEL processes run in global transactions, while other Oracle SOA Suite components, such as adapters, run in local transactions. This can cause inconsistencies with the information displayed in Oracle Enterprise Manager Fusion Middleware Control Console.
Assume you have a main synchronous BPEL process that invokes an asynchronous BPEL process. There is one database adapter insert in the main synchronous BPEL process before the invocation of the asynchronous BPEL process. There is a second database adapter insert in the asynchronous BPEL process, at which point a fault is expected to be thrown.
The expected behavior is as follows:
- An initial insert into the database is performed from the main process that completes successfully as expected.
- The second insert also executes in the asynchronous process, but after encountering the fault, the BPEL process rolls back the initial insert.
However, in Oracle Enterprise Manager Fusion Middleware Control Console, the second database insert also shows as having completed successfully, instead of the having faulted.
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