PK46886: MEMORY LEAK OCCURS AFTER MANY MESSAGE LISTENER PORT RESTARTS | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description A memory leak (and java.lang.OutOfMemoryErrors) may occur in WebSphere Application Server V5.1.1.x after message listener ports are restarted many times. A heap dump would show a leak suspect similar to: . 101,088,720 ■304 5 class com/ibm/ejs/j2c/HandleList 0x3029cba0 101,088,312 ■24 1 java/util/ArrayList 0x307dc4a0 101,088,288 ■13,784 3,056 array of java/lang/Object 0x35ce2530 66,400 ■48 4 com/ibm/ejs/jms/JMSQueueConnectionHandle 0x30bd33b0 65,984 ■48 4 com/ibm/ejs/jms/JMSQueueConnectionHandle 0x30c77a28 65,984 ■48 4 com/ibm/ejs/jms/JMSQueueConnectionHandle 0x33ea75a8 ... - Listener ports could attempt to restart a high number of times if the queue is modified to be GET(DISABLED) or if there is some communication problem between the application server and the queue. On every restart attempt, a com.ibm.ejs.jms.JMSQueueConnectionHandle object is added to the com.ibm.ejs.j2c.HandleList, but these objects are never removed. In time, this leads to high memory consumption and java.lang.OutOfMemoryErrors.Local fix Fix the underlying problem that causes the frequent listener port restarts.Problem summary **************************************************************** * USERS AFFECTED: IBM WebSphere Application Server version * * 5.1 users with message-driven beans (MDB) * * Listener ports that continually restart * **************************************************************** * PROBLEM DESCRIPTION: OutOfMemoryError experienced when * * listener ports continually restart. * * This may be due to an error * * condition, such as a get inhibited * * queue that causes the listener port * * to stop, then attempt to restart. * **************************************************************** * RECOMMENDATION: * **************************************************************** The leak occurred due to the MQ connection used by the listener port being created on one thread, but closed on another. The WebSphere Application Server connection logic associated the connection with the original thread, so did not destroy the object when the connection was closed.Problem conclusion The fix changes the creation of the connection so that it is not associated with a thread. This fix is included in fix pack 5.1.1.17 Please see the recommended fixes page: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 10A
Software edition:
Reference #: PK46886
IBM Group: Software Group
Modified date: Nov 16, 2007
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.