RP/TUX 9.0/TUX 9.1 - In an MP config, aborted trans stay in BB in certain cases, maybe forever (Doc ID 777392.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 9.0,9.1
Information in this document applies to any platform

Goal

DESCRIPTION:
In an MP configuration, when requests come from a machine and require services only from one REMOTE machine
(Coordinator TMS is on the remote machine), then when the client aborts the transaction, the transaction stays in the
TMGABORTED state in the GTT in the BB for as long as the initial transaction timeout (In the customer's case, this
transaction timeout is infinite, so the transactions are filling the GTT).

The 'bankapp' application, implemented with an MP configuration, can be run to prove this.  When the 'bankapp'
services are run on the master site, and then 'tmadmin', 'v' (for verbose), and then 'pt' are executed, the message
'There is no outstanding transaction' is displayed.  However, when the same service is immediately run on the remote
site, and then the same 'tmadmin' steps are repeated, the message 'TMGABORTED' is displayed.

CONFIGURATION:
Tuxedo 9.1
Tuxedo 9.0
Solaris 2.6

Solution

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