RP/TUX 8.0/TUX 9.1 - conversation always AUTOTRAN although AUTOTRAN=N when 3 conditions are met

(Doc ID 775190.1)

Last updated on NOVEMBER 04, 2016

Applies to:

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

Goal

DESCRIPTION:
conv.2172.1832.0: gtrid x0 x40878ba8 x4:      3  >>> NORMAL
conv.2172.1832.0: gtrid x0 x40878ba8 x4:      Ouille !  ==> ERROR
conv.2172.1832.0: gtrid x0 x40878ba8 x4:      Caught ERROR 13 ==> TPETIME, although BLOCKTIME not reached and no
transaction wanted nor configured

CONFIGURATION:
Windows 2000
MODEL MP (even with only 1 machine) (implies OPTION LAN)
tpbegin/tpcall(TOUPPER)/tpcommit before tpconnect(conv)
At least TOUPPER service configured AUTOTRAN
==> the conversational service is called _as_if_ AUTOTRAN was configured

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