PQ57201: NO EXCEPTION THROW WHEN A DB2 ERROR OCCURS

A fix is available
3.5.4-3.5.7, 4.0.2-4.0.7: Component cumulative Connection Manager fix

APAR

APAR status
Closed as program error.

Error description
Problem :  The customer has DB2 XA enironment with one
local and one remote application database.  He shuts
down the remote application database, and the transaction
fails.  Before applying pq55352 (and subsequently pq55402),
an error was returned to the servlet.  Until DB2 apar
JR16724 was applied, the biggest problem was that at
pq48877 the customer received an exception, but the DB2
layer never recovered the XA transaction.
.
With the DB2 apar and PQ48877 the customer application
recovers.  But if they apply pq55402 they still see the
behavior where with the remote database down, the servlet
just hangs, and no exception is every thrown.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 Connection Management                        *
****************************************************************
* PROBLEM DESCRIPTION: Possible hangs when processing          *
*                      StaleConnectionExceptions.              *
*                      Similar to PQ55402.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Possible hangs when processing StaleConnectionExceptions.
Connections become unusable and do not recover. This
is similar to PQ55402 but for a different case - JTA
Enabled or XAConnection.
* RECOMMENDATION: *****************************************************************Possible hangs when processing StaleConnectionExceptions.Connections become unusable and do not recover. This, is similar toPQ55402, but for a different case - JTAEnabled or XAConnection.
Problem conclusion
The code path for JTA was fixed so that it doesn't hang
when a stale connection occurs.
Temporary fix
Customer has the Fix and it works.
Comments
APAR information
APAR numberPQ57201
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-01-28
Closed date2002-04-23
Last modified date2002-04-23

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:

PQ60432

Modules/Macros
JDBC
APAR is sysrouted TO one or more of the following:PQ60432Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ57201
IBM Group: Software Group
Modified date: 2002-04-23