My Oracle Support Banner

OMSG Adapter Unable To Manage Global Transaction Boundary When Datasource Failed To Connect Database (Doc ID 2718943.1)

Last updated on OCTOBER 15, 2020

Applies to:

Oracle Service Bus - Version and later
Information in this document applies to any platform.


On : version, OSB Transports

OMSG adapter unable to manage global transaction boundary when datasource failed to connect database

OMSG adapter used for polling any record from table when status column value is "P" and set the status to "I" when it consumed the messages. Upon successful transaction , the OMSG adapter response back the table to update the status column value to "C".
During Database instance failure, OMSG adapter polled the message from table and status changed to "I". Transaction got completed but OMSG adapter failed to update the status to "C"(Ideally it should do that). If system failure is considered, datasource (XA mode compliant) failed to connect the database and transaction didn't rollback to status "P". It caused the records unattended by application to rollback/complete the transaction.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.