Fixes are available
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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
PM81521;8.0.0.6: messages stuck in pending acknowledgement state in websphere appl
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.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
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
A JMS application publishes messages to a WebSphere Application Server v7.0 Service Integration Bus Topic. Messages on the topicspace start building up when the number of transactions per second is increased. Even when the transactions per second is ramped down, the messages are consumed very slowly. Messages reporting Hung threads and HMGR0152W messages are written to the SystemOut.log: WSVR0605W: Thread "SIBFAPInboundThreadPool : 3" (00000067) has been active for 618131 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:167) at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.Receive ListenerDispatchBarrier.pass(ReceiveListenerDispatchBarrier. java:60) at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.Receive ListenerDispatchQueue.enqueue(ReceiveListenerDispatch Queue.java:313) at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.Receive ListenerDispatcher.queueInvocationCommon(ReceiveListener Dispatcher.java:571) at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.Receive ListenerDispatcher.queueDataReceivedInvocation(Receive ListenerDispatcher.java:667) at com.ibm.ws.sib.jfapchannel.impl.InboundTransmissionParser. dispatchToConversationListenerMethod(InboundTransmission Parser.java:1157) at com.ibm.ws.sib.jfapchannel.impl.InboundTransmissionParser. dispatchToConversation(InboundTransmissionParser.java:996) at com.ibm.ws.sib.jfapchannel.impl.InboundTransmissionParser. parseConversationPayload(InboundTransmissionParser.java: 732) at com.ibm.ws.sib.jfapchannel.impl.InboundTransmissionParser. parse(InboundTransmissionParser.java:293) at com.ibm.ws.sib.jfapchannel.impl.ConnectionReadCompleted Callback.complete(ConnectionReadCompletedCallback.java:249) at com.ibm.ws.sib.jfapchannel.framework.impl.CFWIOReadRequest Context$1.complete(CFWIOReadRequestContext.java:198) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener. futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback (AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions (AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java: 138) at com.ibm.io.async.ResultHandler.complete(ResultHandler. java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop (ResultHandler.java:816) at com.ibm.io.async.ResultHandler$2.run(ResultHandler. java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java: 1550) HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 31 seconds.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for IBM WebSphere Application Server * * version 7.0,8.0 and 8.5 * **************************************************************** * PROBLEM DESCRIPTION: Messages stuck on Messaging engine * * (ME) hosting publication point * **************************************************************** * RECOMMENDATION: * **************************************************************** This problem is seen in a publish subscribe environment. The messages were not flowing from the source ME (the point where the messages were published) to the destination ME (the point where the durable subscription home was defined). This was caused due to a gap in ticks( internal state of the ME) at the source ME (where the messages are stuck). The messages remain in pending acknowledgment mode. This problem comes because the source ME has just now discovered a subscriber is added at the destination ME for first time. On the discovery of this, at the source ME a gap is formed in tick range ( internal book keeping data structure which is used to transfer messages between MEs).
Problem conclusion
The code has been modified to fill the gap in the tick range. This APAR will ensure that message flow between MEs . The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.27 ,8.0.0.7 and 8.5.0.2. 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
PM62615
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-17
Closed date
2012-10-15
Last modified date
2013-03-18
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
WAS SIB & SIBWS
Fixed component ID
620800101
Applicable component levels
R300 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021