APAR status |
Closed as program error.
| Error description
Customer sees many leaked connections following a
TransactionAbortedException from a long running query to a
legacy system. System will hang. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* Connection Management to the database *
****************************************************************
* PROBLEM DESCRIPTION: User sees many leaked connections *
* following TransactionAbortedException *
* from a long running query to a *
* legacy system. System hangs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
There was a case where if the transaction timed out and
rolls back before the application returned from an ejb which
suspended the transaction, then the application tried to
use the connection, they would get a cm exception:
TransactionAbortedException, but the connection would be
leaked. use the connection, they would get a cm exception:TransactionAbortedException, but the connection would beleaked. Problem conclusion
Corrected the code so that in the case where the transaction
timed out, the connection is freed and returned to the pool
correctly. Temporary fixComments
APAR information | APAR number | PQ65313 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-08-15 | Closed date | 2002-09-05 | Last modified date | 2002-09-05 |
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 SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|