Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
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: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
This is a simmilar problem as in APAR PK09766. In this case sequ ence errors occur when NPM spead is set to FAST on MQLINK sender and normal on MQ receiver.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider in * * WebSphere Application Server V6, using a * * WebSphere MQ link to interconnect a * * service integration bus and a WebSphere MQ * * queue manager. * **************************************************************** * PROBLEM DESCRIPTION: Messages stop flowing from the service * * integration bus to the queue manager. * * CWSIC3011E messages are seen in the * * application server logs. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following message is seen in the application server logs: CWSIC3011E: The WebSphere MQ link LINKNAME and the remote queue manager do not agree on the next message sequence number. A message with sequence number 25 has been sent when sequence number 29 was expected. This problem occurs when the nonpersistent message speed (NPMSPEED) property on the receiver channel of the queue manager is set to NORMAL, and the nonpersistent message speed on the WebSphere MQ link is left at the default value of FAST. The negotiation of nonpersistent message speed between the WebSphere MQ Link sender channel and the queue manager receiver was incorrect. This caused the queue manager to use a nonpersistent message speed of normal, while the WebSphere MQ link used a nonpersistent message speed of fast. When nonpersistent messages were sent down this channel, the sequence numbers saved by the WebSphere MQ Link and the queue manager became out of synchronization.
Problem conclusion
This APAR resolves the problem. If CWSIC3011E messages were observed before applying this APAR, it is necessary to reset the WebSphere MQ Link sender channel before it can be restarted. Note that there may be other causes of CWSIC3011E errors, this APAR only fixes the case where the cause is the non-matching NPMSPEED settings.
Temporary fix
Comments
APAR Information
APAR number
PK49927
Reported component name
PLAT MSG COM
Reported component ID
620400101
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-07-27
Closed date
2007-08-13
Last modified date
2007-08-13
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
620400101
Applicable component levels
R100 PSY
UP
Document Information
Modified date:
29 December 2021