PK70854: THE MAXIMUM FAILED DELIVERIES SETTING IS NOT BEING ENFORCED WHEN USING A WEBSPHERE MQ SERVER ON Z/OS AS A BUS MEMBER

Fixes are available

APAR status

Closed as program error.

Error description

The following error may be seen when a message consumer rolls
back after reading a message from a WebSphere MQ server:

CWSIP0002E: An internal messaging error occurred in
com.ibm.ws.sib.processor.impl.RMQConsumerManager,
1:510:1.26.1.1,
com.ibm.ws.sib.processor.impl.exceptions.RMQResourceException:
CWSIP0815W: A message could not be received from destination
myMQDestination assigned to WebSphere MQ Server bus member
MQQM-myBus. The WebSphere MQ completion code was 2. The
WebSphere MQ reason code was 2033.

This error may also cause the message to be delivered more
times than the maximum failed deliveries setting.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  WebSphere Application Server v6.1 or v7.0   *
*                  using a WebSphere MQ server as a bus member.*
****************************************************************
* PROBLEM DESCRIPTION: When a consumer cannot process a        *
*                      message from a bus destination hosted   *
*                      on a WebSphere MQ queue manager         *
*                      configured as a bus member (via a       *
*                      WebSphere MQ Server object),            *
*                      it is likely to be delivered to the     *
*                      consumer more times than the maximum    *
*                      failed deliveries configured on the     *
*                      destination.                            *
*                                                              *
*                      A CWSIP0002E error may be seen,         *
*                      caused by a MQJE001 error with          *
*                      completion code 2 and reason code       *
*                      2033 MQRC_NO_MSG_AVAILABLE.             *
*                      The error may be seen multiple times.   *
*                      The failure will be accompanied with    *
*                      an FFDC similar to this.                *
*                                                              *
*                      ------Start of DE processing------ =    *
*                       20/08/08 14:09:03:655 BST  , key =     *
*                      com.ibm.mq.MQException                  *
*                      com.ibm.ws.sib.remote.mq.impl.          *
*                                  QueueImpl.delete 1:686:1.63 *
*                      Exception = com.ibm.mq.MQException      *
*                      Source = com.ibm.ws.sib.remote.mq.      *
*                                        impl.QueueImpl.delete *
*                      probeid = 1:686:1.63                    *
*                      Stack Dump = com.ibm.mq.MQException:    *
*                      MQJE001: Completion Code 2, Reason 2033 *
*                      at com.ibm.mq.MQQueue.getMsg2(          *
*                                           MQQueue.java:1078) *
*                                                              *
*                      The message will be redelivered and     *
*                      processed again.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Exception handling was incorrect for messages being read from
a WebSphere MQ queue manager configured as a default messaging
bus member.

Messages are marked in WebSphere MQ (by the bus) to prevent
multiple consumers accessing a message concurrently.  When a
failure occurred the bus rolled back the message onto the
queue (unmarking it and making it available to other
consumers) before it attempted to move it to the exception
destination. There was a timing window between the unmark of
the rollback and the mark for the move to the exception
destination where another consumer could try to mark the
message.  If this happened the second thread to attempt the
mark would show the CWSIP0002E/MQJE001 error.

Also, if the exception destination is configured to be another
WebSphere MQ queue and there is a problem putting the message
to that destination (for example, because the queue is full) a
CWSIP0002E error may happen repeatedly and the message will
be repeatedly reprocessed from the original destination.
In this case each CWSIP0002E message is accompanied with an
FFDC showing "MQJE001: Completion Code 2, Reason 2053", where
2053 is the reason the message could not be sent to the
exception destination (MQRC_Q_FULL in this example).
The correct behavior is for the message to be moved to system
exception destination if there are problems using the
user-defined exception destination.
For more information on WebSphere MQ reason codes refer to:
http://www.ibm.com/support/docview.wss?rs=171&uid=swg21232330
and
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?to
pic=/com.ibm.mq.csqzaq.doc/csqzaq00221.htm

Problem conclusion

This APAR updates the rollback handling of messages with
WebSphere MQ servers configured as a bus member, so that
messages are correctly delivered to the user defined exception
destination when the maximum failed delivery threshold is
reached (or the system exception destination if the user
defined exception destination is full).

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.23 and 7.0.0.3.  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
PK70854
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
2008-08-20
Closed date
2008-09-19
Last modified date
2009-06-08

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

PK70854: THE MAXIMUM FAILED DELIVERIES SETTING IS NOT BEING ENFORCED WHEN USING A WEBSPHERE MQ SERVER ON Z/OS AS A BUS MEMBER

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?