APAR status |
Closed as program error.
| Error description
When using JTA, they get this exception if t
connection is bad and it's not mapped to staleConnection. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Connection *
* Manager users. *
****************************************************************
* PROBLEM DESCRIPTION: SQLException not mapped to *
* StaleConnectionException when it *
* should be. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using JTA, there was a case where a Stale Connection
was being used (doing a SetAutoCommit) and the SQLException
was not mapped to StaleConnectionException when it should
have been. Problem conclusion
Try/catch blocks code was added around setAutoCommit
to ensure that translateException() is called to map the
exception to a StaleConnectionException if applicable. Temporary fixComments
APAR information | APAR number | PQ61397 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-05-21 | Closed date | 2002-05-28 | Last modified date | 2002-05-28 |
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:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|