PM90908: JMS APPLICATION RECEIVED MQRC=2069 (MQRC_SIGNAL_OUTSTANDING)

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer's JMS Application got MQRC=2069 MQRC_SIGNAL_OUTSTANDING
  (in this case, JMS application is launched by JZOS Java Batch
  Launcher) when consumer issued receive API. Stack Trace shows:
   Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ
  call failed with compcode '2' ('MQCC_FAILED') reason '2069'
  ('MQRC_SIGNAL_OUTSTANDING').
    at
  com.ibm.msg.client.wmq.common.internal.Reason.createException(Re
  ason.java:223)
  .
  Search keywords:
  MQRC_SIGNAL_OUTSTANDING MQRC 2069 RC2069
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1 and Release 1       *
  *                 Modification 0.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: JMSCMQ0001 reports MQ call failure with *
  *                      reason '2069'                           *
  *                      ('MQRC_SIGNAL_OUTSTANDING') when a      *
  *                      consumer calls receive() shortly after  *
  *                      a different consumer on the same        *
  *                      session is closed.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During the close of a Message Consumer, the MQ JMS classes call
  spiNotify to post any outstanding get waiters for the
  connection. In rare cases the asynchronous post issued by
  spiNotify (CSQMSNTF) does not take effect until after the close
  completes. This can lead to a subsequent receive(time) issued
  against a different consumer being posted unexpectedly causing
  the MQGET to return MQRC_XWAIT_CANCELED to the MQ JMS classes.
  The MQ JMS classes detect the requested interval has not passed
  and reissue the MQGET, however this fails immediately with
  MQRC_SIGNAL_OUTSTANDING, and the receive raises an MQException.
  

Problem conclusion

• CSQMSNTF has been changed to only post handles that are
  currently on the getwait chain.
  010Y
  100Y
  CSQMSNTF
  CSQMTCON
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK95776 UK95777

Modules/Macros

• CSQMSNTF CSQMTCON
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK95776

     UP13/08/23 P F308

• R100 PSY UK95777

     UP13/08/23 P F308

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.