Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Messages build up on Websphere Application Server v6.1.x Service Integration Bus Topic Destination Javacores collected from the JVM hosting the messaging engine show a livelock where thread 1 waits to acquire a lock indefinitely while another thread, thread 2, holds the lock. Thread 2 is not blocked, but never releases the lock. Thread 1: at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint.close (JSLocalConsumerPoint.java:2766(Compiled Code)) at com/ibm/ws/sib/processor/impl/ConsumerSessionImpl._close (ConsumerSessionImpl.java:619(Compiled Code)) at com/ibm/ws/sib/processor/impl/ConnectionImpl._close (ConnectionImpl.java:593(Compiled Code)) at com/ibm/ws/sib/processor/impl/ConnectionImpl.close (ConnectionImpl.java:489(Compiled Code)) at com/ibm/ws/sib/comms/server/clientsupport/ServerTransport ReceiveListener.cleanupConnection(ServerTransportReceive Listener.java:922(Compiled Code)) at com/ibm/ws/sib/comms/server/clientsupport/ServerTransport AcceptListener.removeAllConversations(ServerTransportAccept Listener.java:273(Compiled Code)) ... Thread 2: ... at com/ibm/ws/sib/comms/server/clientsupport/CATProxyConsumer. sendMessage(CATProxyConsumer.java:758(Compiled Code)) at com/ibm/ws/sib/comms/server/clientsupport/CATAsynchReadAhead Reader.consumeMessages(CATAsynchReadAheadReader.java:130 (Compiled Code)) at com/ibm/ws/sib/processor/impl/AsynchConsumer.processMsgs (AsynchConsumer.java:105(Compiled Code)) at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint.process AttachedMsgs(JSLocalConsumerPoint.java:2015(Compiled Code)) at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint.runAsynch Consumer(JSLocalConsumerPoint.java:2705(Compiled Code)) at com/ibm/ws/sib/processor/impl/JSLocalConsumerPoint$Asynch Thread.run(JSLocalConsumerPoint.java:2931(Compiled Code)) at com/ibm/ws/util/ThreadPool$Worker.run(ThreadPool.java:1497 (Compiled Code))
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: Messages continue to accumulate for a * * subscriber that has disconnected. * **************************************************************** * RECOMMENDATION: * **************************************************************** A live lock during the disconnection of a non-durable subscriber (usually due to a network outage) can prevent the de-registration of the subscriber from the messaging engine. This results in the accumulation of messages for this subscriber eventually resulting in the destination depth threshold (CWSIP0553W) being reached or the message store becoming full (CWSIS1575E). Unexpected CPU load on the server hosting the messaging engine will also occur. This live lock is the result of read ahead consumers (subscribers are read ahead consumers by default) failing to stop the consumer when the connection the read ahead consumer is attempting to send data to is closed asynchronously. While sending message data, the consumer holds a lock. This lock is needed to cleanup the connection, so the cleanup cannot proceed until the consumer stops.
Problem conclusion
This APAR resolves the problem by stopping the consumer when the connection is closed. Thus the lock is released and the connection cleanup can proceed. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.41 and 7.0.0.19. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Disable read ahead.
Comments
APAR Information
APAR number
PM34003
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-03
Closed date
2011-05-24
Last modified date
2011-05-24
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
PLAT MSG COM
Fixed component ID
620600101
Applicable component levels
R200 PSY
UP
Document Information
Modified date:
27 October 2021