APAR status |
Closed as program error.
| Error description
Customer application hangs after upgrading to 3.5.6. They have
a deadlock in WebSphere at a point where they get a
translateexception that is in the process of closing the
connections to the database for a staleconnectionexception. This
deadlocks with the alarm thread which is processing a rollback
for a transaction timeout. Local fixProblem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of *
* Connection Pooling *
****************************************************************
* PROBLEM DESCRIPTION: Users may see a hang condition *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A condition existed where a deadlock could happen when
a StaleConnectionException was closing a connection and
at the same time the Alarm thread for transaction
timeout was causing a rollback. Problem conclusion
The problem was that the alarm had a lock on the connection
proxy and was trying to get a lock on the statement proxy,
the StaleConnectionException processing has a lock on the
statement proxy and was trying to get a lock on the
connection proxy. Locking now has been revised so this
cannot happen. Temporary fixComments
APAR information | APAR number | PQ63031 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-07-10 | Closed date | 2002-08-20 | Last modified date | 2002-11-12 |
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:
PQ68152
Modules/Macros APAR is sysrouted TO one or more of the following:PQ68152Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|