Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo / Tuxedo / 8.1,9.1
Information in this document applies to any platform
DESCRIPTION: If a Tuxedo server program crashes after starting a transaction, the transaction does not get aborted for "timeout" value specified in the call to tpbegin(). This condition happens only when the application program is configured with RESTART=Y. When RESTART=N, the transaction aborts in about 2 - 3 minutes consistently irrespective of the "timeout" value specified in tpbegin(). The following are the conditions observed, when the server application that intiated the transaction crashed -or- was killed. 1) Restart=Y, timeout=0: Transaction does not timeout at all. 2) Restart=Y, timeout=600: Transaction times out in 600 seconds 3) Restart=N, timeout=0: Transaction times out in approx 2 minutes. 4) Restart=N, timeout=600: Transaction times out in approx 2 minutes. Customer Requirement : They specify a transaction timeout of 10 minutes. When RESTART=Y, if the server crashes, they wait for 10 minutes to restart the transaction. When RESTART=N, the transation aborts in about 2 minutes. Why would RESTART=Y make a difference in a transaction timeout? They want this to be fixed so that when a server crash, the transaction aborts in a consistently smaller timeframe so that it can be restarted ASAP. This irrespective of whether RESTART=Y -or- N.
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