PI06190: AFTER MDB PROCESS OF JMS-TOPIC, THE LISTENER PORT IS RESTARTED BECAUSE THE TEMPORARY QUEUE HAD BEEN DELET 13/11/28 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After the MDB processing of Jms-Topic is over, and 30 minutes
  passed, temporary queue is disappeared for some reason. as a
  result, a listener port restarts.
  .
  The traces show that the server session gets a handle to the
  managed queue by calling lpiSpiSubscribe, and passing the SubId
  of the subscription. This call returns a handle to the
  destination queue, but no subscription handle.
  When the server session closes the handle to the queue,
  because its a managed queue, a check is made that the associated
  subscription handle is still valid. In this instance there is no
  associated subscription handle, and so CSQMCLS2 incorrectly
  determines that the subscription no longer exists and deletes
  the managed queue.
  

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: MDB using non-durable subscriptions     *
  *                      fails MQRC_Q_DELETED after server       *
  *                      session reaches                         *
  *                      SERVER.SESSION.POOL.UNUSED.TIMEOUT.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An MDB listening on a topic connection creates a non-durable
  subscription, which creates a managed dynamic queue for the
  lifetime of the subscription.
  A message is published to the topic, and a server session is
  started to process the message.
  After PM71101 is applied, the server session gets a handle to
  the managed queue by calling lpiSpiSubscribe, and uses this
  handle to get the publication from the managed queue.
  If the server session is closed due to reaching the
  configured unused timeout, its handle to the queue is closed,
  and because the handle is incorrectly flagged as being linked
  to a subscription handle, this results in the queue being
  prematurely deleted.
  When the message listener attempts to browse the managed
  queue for subsequent messages it fails with MQRC_Q_DELETED
  (MQRC 2052).
  

Problem conclusion

• CSQMSUB/CSQMSUBI is changed to no longer link the destination
  queue handle with a non-existent subscription handle when
  lpiSpiSubscribe is called to get a handle to a managed queue,
  preventing the queue being prematurely deleted when the
  destination handle is closed.
  010Y
  100Y
  CSQMSSUB
  CSQMSUB
  CSQMSUBI
  CSQMSUBV
  

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:

  UI13084 UI13085

Modules/Macros

• CSQMSSUB CSQMSUB  CSQMSUBI CSQMSUBV
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UI13084

     UP13/12/24 P F312 Ø

• R100 PSY UI13085

     UP13/12/24 P F312 Ø

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.