APAR status
Closed as program error.
Error description
WebSphere maps several SQL exceptions to the
StaleConnectionException. It only checks the top of the
exception stack to see if it should map a SQL exception to a
StaleConnectionException. There are cases where the top
exception in the stack would not map to a
StaleConnectionException but sub-exceptions would.
WebSphere should check the sub-exceptions to see if the root
cause would be a StaleConnectionException and map the current
exception appropriately.
For example, the stack below should have been a
StaleConnectionException even though the HY000 error doesn't
map to a StaleConnectionException - the 08S01 error does:
SQL STATE: HY000
ERROR CODE: 0
java.sql.SQLException: [IBM][SQLServer JDBC Driver]Exception
generated during defered local transaction handling. See next
exception via SQLException.getNextException for details.
at
com.ibm.websphere.jdbc.base.BaseExceptions.createException(Unkno
wn Source)
at
...
---- Begin backtrace for Nested Throwables
SQL STATE: 08S01
ERROR CODE: 0
java.sql.SQLException: [IBM][SQLServer JDBC Driver]Connection
reset by peer: socket write error
at
com.ibm.websphere.jdbc.base.BaseExceptions.createException(Unkno
wn Source)
...
This problem was reported on WebSphere 5.1.1.3 on Windows 2003
using the SQLServer 3.3.50 driver with both XA and non-XA
enabled datasources, with the enable2Phase setting set to false.
Local fix
Different versions of the driver (XA or non-XA) or different
settings on that driver (enable2Phase true or false) might
change the order of exceptions thrown causing an exception
mapped to StaleConnectionException to be at the top of the
stack.
Also, it is possible to create a custom dataStoreHelper class
and map the top exception to the StaleConnectionException
manually.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of *
* Relational Resource Adapter. *
****************************************************************
* PROBLEM DESCRIPTION: StaleConnectionExceptions (SCEs) were *
* not thrown when they should have been. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
In some cases dataBase vendors may choose to have linked
exceptions to further define the error they are throwing.
In many cases the top level exception is not appropriate for
us to map it to our StaleConnectionException, however
the linked exception is.
Problem conclusion
StaleCOnnectionExceptions are now thrown in the
appropriate place. We now will look at all linked exceptions
for exception which are deemed to be SCE.
The fix for this APAR is currently targeted for inclusion
in cumulative fixes 5.02.14 and 5.1.1.8 and fixpack 6.0.2.5.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK11153 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-08-30 |
Closed date |
2005-11-01 |
Last modified date |
2005-11-01 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
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 |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|