PI61141: WMQ JAVA THREADS FOR MQGET HANG AFTER WEBSPHERE MQ JMS MAINTENANCE IS APPLIED 16/05/04 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Code introduced through PI52987/UI33363 can impact applications
  using an RRS enabled connection to WebSphere MQ ( including
  bindings mode connections from WAS ) When a connection to MQ is
  in an MQGET wait and either a message arrives or the wait
  interval expires, the code to post the waiting task can
  incorrectly determine that the task is no longer valid and skip
  the post call. This results in the connection remaining
  permanently suspended in the MQGET wait.
  .
  Additional keywords:
  WebSphere Application Server WAS WSAS
  IBM Integration Bus (formerly WebSphere Message Broker)
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
  *                 Release 0 Modification 0                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: After applying UI33363, RRS             *
  *                      applications (including IIB and WAS)    *
  *                      issuing MQGET calls can hang            *
  *                      indefinitely if the MQGET is issued on  *
  *                      a different TCB to that originally used *
  *                      by a context, and the original TCB is   *
  *                      no longer active.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a getting application is being posted (for example, by the
  arrival of a suitable message, or the expiry of the get wait
  interval), code added to CSQM1P1W by PI52987 checks if the
  getter TCB is still active if there are any tasks in the getter
  address space in EOT processing.
  This check uses the tcbtoken stored in the getter's MTHR,
  however if the MQGET call was issued on a different TCB to the
  TCB the context originally used, the tcbtoken is incorrect and
  still relates to the original TCB. If that TCB has ended,
  CSQM1P1W incorrectly determines that the getter is going through
  EOT processing and skips posting the getter's ECB, leading to
  the reported problems.
  

Problem conclusion

• CSQMGET is changed to ensure the MTHR associated with an RRS
  MQGET request is updated with the correct tcbtoken for the TCB
  currently being used for the MQGET request, allowing the check
  in CSQM1P1W to correctly determine if that TCB is still active
  or not.
  000Y
  CSQMALL
  CSQMCETH
  CSQMGET
  CSQM1P1W
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  PI61683 UI37798

Modules/Macros

• CSQMALL  CSQMCETH CSQMGET  CSQM1P1W
  

Fix information

• Fixed component name

  WMQ Z/OS 8

• Fixed component ID

  5655W9700

Applicable component levels

• R000 PSY UI37798

     UP16/05/26 P F605 «

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.