RP/TUX 8.1/TUX 9.1 - Request to propagate CR121000 (Doc ID 777195.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 25-07-2011***

Goal

DESCRIPTION:
Please propagate CR121000 to Tuxedo 8.1.

There was a problem that application data was partially committed.
The transaction can be summarized as follows:
  1. A service 'BSMLINK' does:
      tpbegin();
      tpcall("DAX0000")
      tpcall("FXMAIN")
      tpcommit();
  2. DAX0000 executes some SQL's and tpreturn
  3. FXMAIN: tpforward("SP03")
  4. SP03:
      if (tpgetlev() == 0) {
          tpbegin();
          localbegin = 1;
      }
      do some SQL's
      if (localbegin) tpcommit()
      tpreturn()

The problem is:
  the SQL's of DAX0000 were rolled back and
  the SQL's of SP03 were committed.

At that time, SP03 was running slowly and there were a lot of requests in the queue of SP03. The request was in the
queue of SP03 for about 38 seconds (this is not a problem). The SQL's of DAX0000 seemed to be rolled back by Oracle
because of SesTm(=30) timeout and the SQL's of SP03 was committed because they are executed within the new transaction
issued by SP03.

CONFIGURATION:
Tuxedo 8.1 64bit RP203
AIX 5.2
Oracle 9i

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