PQ72386: STALECONNECTIONEXCEPTION CLEANUP MAY RESULT IN AN SQL EXCEPTION WITH MESSAGE TEXT "INVALID TRANSACTION STATE"

 Fixes are available

WebSphere Application Server Connection Manager Cumulative Fix
5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
If a StaleConnectionException occurrs during a transaction, but
the connection itself is still valid, the
StaleConnectionException cleanup may result in an SQL Exception
with the message text "Invalid Transaction State."  This is
because an attempt is made to close the connection to the
database without rolling back the connection.  Need to add code
to roll back the connection prior to closing the connection.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users running   *
*                 in a transactions environment and            *
*                 encountering a StaleConnectionException      *
*                 where the connection itself is still valid.  *
****************************************************************
* PROBLEM DESCRIPTION: If a transactional application          *
*                      encounters a StaleConnectionException   *
*                      while running, but the connection       *
*                      itself is still valid (for example,     *
*                      an illegal statement handle exception   *
*                      on DB2 is translated to                 *
*                      StaleConnectionException, but only the  *
*                      statement is bad, the connection itself *
*                      is still valid), the connection manager *
*                      attempts to close the connection before *
*                      rolling back the transactional work,    *
*                      resulting in an exception due to the    *
*                      illegal transaction state (actual       *
*                      exception will be slightly different    *
*                      depending on the backend).              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Because of the call to pooledconnection.close() before the
work on the connection was rolled back, an invalid
transaction state exception was thrown.
Problem conclusion
Modified the code to roll back the transaction before calling
the close method.
Temporary fix Comments
APAR information
APAR number PQ72386
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-03-24
Closed date 2003-04-03
Last modified date 2003-04-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JDBC          

Publications Referenced

Fix information

Applicable component levels
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ72386
IBM Group: Software Group
Modified date: Apr 3, 2003