PQ68152: WEBSPHERE INTERMITTANTLY HANGS UNDER HEAVY LOAD WHEN IT LOSES CONNECTION TO THE DATABASE. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() 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 fix Problem 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 fix Comments
APAR is sysrouted FROM one or more of the following: PQ63031 APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ68152
IBM Group: Software Group
Modified date: Nov 12, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.