Fixes are available
PM71430; 8.0.0.5: pubsub messages stuck on WebSphere Application Server SIB
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
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.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
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
A JMS application publishes messages to WebSphere Application Server Service Integration Bus publication point. The published messages are delivered to the consumers successfully but the messages still remain on the publication point. This leads to a build up of messages on the destination. The following errors are written to the SystemOut.log: CWSIA0067E: An exception was received during the call to the method JmsMsgProducerImpl.sendMessage (#4): com.ibm.ws.sib. processor.exceptions.SIMPLimitExceededException:CWSIP0251E: The destination XXXTopicSpace on messaging engine XYZ is not available because the high limit 50,000 for the number of messages for this destination has already been reached..
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: PubSub messages are stuck on WebSphere * * Application Server Service * * Integration Bus * **************************************************************** * RECOMMENDATION: None * **************************************************************** In the publish/subscribe domain, the messages produced on topics move across messaging engines if there are more than one messaging engine in an Application Server environment. This allows consumers running on remote messaging engines to receive messages. The messaging engine where messages are produced is called the source messaging engine and the messaging engine where messages are received is called the target messaging engine. In this communication, when the target messaging engine receives the messages, it searches for the local consumers to dispatch the messages. If there are no consumers, a silence is written for each message received. The silence indicates that the target side is aware of the message being received. In addition to writing silence, it will also send an acknowledgment to the source messaging engine. Once the source messaging engine receives the acknowledgment, it will remove the message. However, it is observed that no acknowledgment is being sent to the source messaging engine. Because of this, the source messaging engine will not remove these messages and the messages pile up on its side.
Problem conclusion
To fix the problem, an acknowledgment is sent from the target messaging engine to the source messaging engine after every 50 consecutive silences. This gap of 50 silence messages is chosen because sending acknowledgment for every silence message may cause network overhead. If any local consumers come up any time, an acknowledgement is always sent during the message delivery. This is a specific scenario in which there are no local consumers on the target side for a long time which results in never acknowledging messages received. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.27, 8.0.0.6 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
PM71430
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-23
Closed date
2012-10-23
Last modified date
2013-05-25
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
R800 PSY
UP
Document Information
Modified date:
29 October 2021