APAR status
Closed as program error.
Error description
When the physical connection to the database became bad for some
reason, application expects to get StaleConnectionException but
it gets the NullPointerException instead.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users who *
* use Connection Pooling. *
****************************************************************
* PROBLEM DESCRIPTION: A small window existed where a *
* NullPointerException would *
* be returned instead of a *
* StaleConnectionException. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A window existed whereby if a
connection to the database went
bad during a user transaction,
We try to rollback a connection
which has already been rolled back.
Problem conclusion
We added a check so we would not try and
rollback the connection twice.
Temporary fix Comments
APAR information |
APAR number |
PQ78561 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A2200 |
Reported release |
400 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Submitted date |
2003-09-16 |
Closed date |
2003-10-01 |
Last modified date |
2003-10-01 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PQ79103
Modules/Macros
SRLS
Applicable component levels |
R400 PSY |
UP |
|