Global Transaction Only Abort After Transaction Timeout When No TMS Server On Remote Group
Last updated on FEBRUARY 14, 2017
Applies to:Oracle Tuxedo - Version 184.108.40.206.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 rollbacked.
Is there a way to allow an immediate rollback when no TMS in one group engaged in global transaction (more that one resourse)?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms