PK79499: AN MQLINK RECEIVER CHANNEL FAILS TO START BECAUSE OF A SEQUENCE NUMBER ERROR (CWSIC3015E)

Fixes are available

APAR status

Closed as program error.

Error description

The MQLink Receiver Channel fails to read the message sequence
number information from the message store because the sequence
number data is locked.  This usually happens because the
data is being updated when the messaging engine's database has
become unresponsive (for example during an online
backup).  After some time, the WMQ Sender Channel will try
to restart the channel but, because the sequence number data
is locked, the MQLink Receiver expects the next sequence
number is 1.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider's   *
*                  MQLink Receiver Channel, which is receiving *
*                  messages from WebSphere MQ (WMQ)            *
****************************************************************
* PROBLEM DESCRIPTION: An MQLink Receiver Channel fails to     *
*                      start due to a message sequence         *
*                      number mismatch. A CWSIC3015E message   *
*                      is logged.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The MQLink Receiver Channel fails to read the message sequence
number information from the message store because the sequence
number data is locked.  This usually happens because the
data is being updated when the messaging engine's database has
become unresponsive (for example during an online
backup).  After some time, the WMQ Sender Channel will try
to restart the channel but, because the sequence number data
is locked, the MQLink Receiver expects the next sequence
number is 1.

The SystemOut log contains the following message:

"CWSIC3015E: The WebSphere MQ link To MQ and the remote queue
manager do not agree on the next message sequence number.  A
message with sequence number <x> has been received when
sequence number 1 was expected."

A channel RESET command must be used to restart the
channel.

As a workaround, you can increase the WMQ Sender Channel HBINT
parameter to delay the Sender Channel's attempt to restart the
channel.

Problem conclusion

To prevent the sequence number mismatch, the MQLnk Receiver
does not try to start if the sequence number data is locked,
even if 'adoption' is enabled.  The WMQ Sender channel
logs the following message at the queue manager:

"AMQ9558: The remote channel '<channel name>' is not currently
available."

When the messaging engine's database  becomes responsive, the
sequence number data is unlocked and the channel can restart.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.0.2.35, 6.1.0.25 and 7.0.0.5.  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
PK79499
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
2009-01-27
Closed date
2009-02-26
Last modified date
2009-04-17

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

[{"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

PK79499: AN MQLINK RECEIVER CHANNEL FAILS TO START BECAUSE OF A SEQUENCE NUMBER ERROR (CWSIC3015E)

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

R200 PSY

Document Information

Share your feedback

Need support?