PQ71069: STALECONNECTIONEXCEPTION IS NOT BEING THROWN FOR 08S01 SQLCODE FOR DATADIRCET DRIVER

 Fixes are available

5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)
5.0.1: WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1



APAR status
Closed as program error.

Error description
SQLException 08s01 is not being translated to a
StaleConnectionException for the datadirect jdbc driver due to a
overlap with the GenericDataStoreHelper. User ends up with a
Socket WrRite Error
Local fix
-30Problem can be worked around by doc found at:

http://publib7b.boulder.ibm.com/wasinfo1/en/info/ae/ae/rdat_levp
ort.html
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 Data Direct Connect JDBC 3.1                 *
****************************************************************
* PROBLEM DESCRIPTION: Connection reset by peer: socket write  *
*                      error ErrorCode=0 SQLState=08S01 is     *
*                      not being mapped to StaleConnection-    *
*                      Exception.                              *
*                                                              *
*                      Therefore the application can't catch   *
*                      it and re-open the connection.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Some of the exception mappings used in DataDirectDataStore-
Helper were removed because they were inconsistent with other
genericDataStoreHelpers (some were not
StaleConnectionExceptions).  One of the ones that we weren't
sure of is ErrorCode=0 SQLState=08S01 - which turns out to
be a StaleConnectionException.

If the mapping is not present for an ErrorCode / SQLState
combination, the SQLException is not wrappered and the
application code will be not know that it should re-open the
connection.

The problem has been fixed under internal defect 158520.
Problem conclusion
The correct mapping has been added to
DataDirectDataStoreHelper so the StaleConnectionException will
be thrown in the future.  A temporary workaround is for the
customer to create their own DataStoreHelper, per the
instructions at this URL:

http://publib7b.boulder.ibm.com/wasinfo1/en/info/ae/ae/
rdat_levport.html
(URL wrapped due to size limitations)
Temporary fix
A temporary workaround can be done by creating a custom
DataStoreHelper, instructions can be found at

http://publib7b.boulder.ibm.com/wasinfo1/en/info/ae/ae/-
rdat_levport.html

after removing the hyphen between /ae/rdat_levport.html.
Comments
APAR information
APAR number PQ71069
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00I
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-02-17
Closed date 2003-02-28
Last modified date 2003-02-28

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
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
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: 00I
Software edition:
Reference #: PQ71069
IBM Group: Software Group
Modified date: Feb 28, 2003