PQ97189: WHEN CONNECTION RECEIVES SQL CODE -30080 OR -924, THIS SHOULD BECONVERTED TO STALECONNECTIONEXCEPTION, AND CONNECTION RE-USED

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
WebSphere, as part of it's processing, will convert certain SQL
codes, to 'StaleConnectionExceptions'.  This APAR is being taken
to add -924 and -30080 to the list of SQL codes which are
converted.
When a StaleConnectionException is thrown, the connection is
reset in the WebSPhere connection pool.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: A java.sql.SQLException with an SQLCODE *
*                      of -924 or -30080 is thrown from DB2    *
*                      but is not getting mapped to a          *
*                      StaleConnectionException.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A java.sql.SQLException from DB2 with an SQLCODE of -924 or
-30080 represents a permanent error condition on the JDBC
connection used to connect to DB2.  Currently, these exceptions
are being thrown to the application with no additional
processing.  These exceptions should be mapped to a
StaleConnectionException and the connection that received the
exception should be marked as stale so it can be purged from
the connection pool.

This problem can be spotted by noticing that your application
is repeatedly receiving a java.sql.SQLException with an SQLCODE
of -924 or -30080.  Receiving the exception numerous times may
indicate that the connection is not getting purged from the
connection pool.
Problem conclusion
WebSphere now properly maps java.sql.SQLExceptions with an
SQLCODE of -924 or -30080 to a StaleConnectionException, and the
connection that received the exception is marked as stale.

APAR PQ97189 is associated with SERVICE LEVEL W502020 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ97189
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-11-15
Closed date 2004-12-15
Last modified date 2005-01-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ97190 PQ99291

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ96100    UP04/12/21 P F412

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ97189.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ97189
IBM Group: Software Group
Modified date: Jan 10, 2005