Global Transaction Only Abort After Transaction Timeout When No TMS Server On Remote Group
(Doc ID 1960916.1)
Last updated on MAY 19, 2020
Applies to:Oracle Tuxedo - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
With distributed transaction across domain, while tpcommit() without a TMS servers on the remote group there is no error sent back to domain coordinator.
The global transaction will be aborted only after the transaction timeout had been occured. This means that all other transaction branches are locked for nothing as at the end the global transaction will be roll backed.
Is there a way to allow an immediate rollback when no TMS in one group engaged in global transaction (more that one resource)?
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