XA Branch Cannot See Commited Data from Another XA Branch during 2PC XA Transaction using 2 Data Sources on Same Database
(Doc ID 2125991.1)
Last updated on AUGUST 09, 2023
Applies to:JDBC - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
An intermittent issue related to read only optimization of two phase commit ( 2PC) within Oracle database is experienced.
The IBM BPM 8.5 transaction manager uses 2 Oracle XA data sources. Both data sources connect to the same 18.104.22.168 database running on the IBM AIX platform.
Transaction 1 on one data source is being processed, then commits to the database (part of the transaction is an insert into a processContext table).
• The BPEL engine will trigger an onward navigation (in-memory) message as part of the afterCompletion processing.
• The in-memory message is being picked up by a worker thread, which then starts transaction 2.
• Transaction 2 on the second data source attempts to do a so-called dummy update on the processContext entry in order to "lock" the process instance.
• However, the update returns with "no rows updated", i.e. transaction 2 is not able to see the data supposedly committed by transaction 1
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