PK88213: SHUTTING DOWN AN APPLICATION SERVER WITH A LARGE NUMBER OF LISTENER PORTS CREATES EXCESSIVE THREADS

Fixes are available

APAR status

Closed as program error.

Error description

When shutting down an application server with many Listener
Ports configured, an excessive number threads may be spawned.
This further increases the shutdown time and may cause the
server to run out of memory, resulting in OutOfMemoryErrors.

Local fix

Stop the listener ports before stopping the application server.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Version 6.1 or 7.0, using WebSphere MQ as   *
*                  a messaging provider                        *
****************************************************************
* PROBLEM DESCRIPTION: Application servers configured with     *
*                      many Listener Ports might report        *
*                      OutOfMemoryError exceptions during      *
*                      shutdown                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During shutdown an application server quiesces its listener
ports. The length of time taken to shutdown an application
server increases with the number of Listener Ports configured.
The Listener Ports are repeatedly asked to quiesce until they
are shutdown.
The issue is that each request spawns a new thread, even
though an existing thread might be active quiescing the
listener port.
Each thread further slows MDB quiesce processing, and
if there are many Listener Ports, the number of threads
spawned can eventually cause the server to run out of native
memory, resulting in OutOfMemoryError exceptions.

A javacore taken of a server experiencing this issue shows a
very large number of threads (significantly more than the
number of listener ports defined) with the following stack:
java/lang/Object.wait(Native Method)
java/lang/Object.wait(Object.java:199(Compiled Code))
com/ibm/mq/jms/MQQueueAgentThread.waitForEnd(MQQueueAgentThread
com/ibm/mq/jms/MQQueueAgent.removeBrowser(MQQueueAgent.java:141
com/ibm/mq/jms/MQConnectionBrowser.stop(MQConnectionBrowser.jav
com/ibm/mq/jms/MQConnection.notifyBrowsers(MQConnection.java:23
com/ibm/mq/jms/MQConnection.stop(MQConnection.java:1162(Compile
com/ibm/ejs/jms/JMSConnectionHandle.stop(JMSConnectionHandle.ja
com/ibm/ejs/jms/listener/MDBListenerImpl$2.run(MDBListenerImpl.

Problem conclusion

The fix for this APAR ensures that only one thread is spawned
per listener port during shutdown of the server.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.27 and 7.0.0.7.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK88213
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-08
Closed date
2009-07-30
Last modified date
2009-07-30

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60S PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61S PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK88213: SHUTTING DOWN AN APPLICATION SERVER WITH A LARGE NUMBER OF LISTENER PORTS CREATES EXCESSIVE THREADS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60S PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61S PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?