PQ67409: TRANSACTION MANAGER MUST DETECT STALE CONNECTIONS AND RETRY ON A NEW ONE

 Fixes are available

PQ67409, 4.0.4, 4.0.5: JTS Transaction Manager StaleConnection detection added
4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6



APAR status
Closed as program error.

Error description
The Transaction Manager does not handle stale connections
correctly. If a network failure occurs with in-flight
transactions (2 phase commit), the transaction manager is not
able to rollback the resource manager.  It tries once and
receives an XAER_RMFAIL.  It then retries the rollback, but
fails with XAER_PROTO.  Defect 139136.

Also the reconnect to RM logic must throw a transient
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server :      *
*                 When a connection to a Resource Manager      *
*                 is lost any prepared Tx's are not            *
*                 resolved when the RM is back on-line,        *
*                 but resolved at application server           *
*                 restart.                                     *
****************************************************************
* PROBLEM DESCRIPTION: JTS Transaction Manager must detect     *
*                      stale connections and retry on new      *
*                      connections.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The v4.0 transaction manager currently does not handle stale
connections.  If a network failure occurs with in-flight
transactions (2PC), the transaction manager is currently not
able to roll back the resource manager.  It tries once and
receives a XAER_RMFAIL.  It then retries the rollback, but
fails with XAER_PROTO.

The solution is to re-instate the connection and then retry.

Also the reconnect to RM logic must throw a TRANSIENT
exception if the RM is not yet available on the retry.
The retry will then be done again after a short wait.
Problem conclusion
Re-instate connection when the RM is back on-line and
resolve prepared transactions.
Temporary fix Comments
APAR information
APAR number PQ67409
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-10-21
Closed date 2002-11-05
Last modified date 2002-11-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JTSXARI          

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67409
IBM Group: Software Group
Modified date: Nov 5, 2002