IC94647: WEBSPHERE MQ FOR HP NONSTOP SERVER DOES NOT DELETE DYNAMIC QUEUES ON CLOSE IF AN MQGMO_SET_SIGNAL MQGET GMO IS OUTSTANDING.

WebSphere MQ for HP NonStop Server V5.3.1 fix pack 5.3.1.10

APAR status

• Closed as program error.

Error description

• On HP Nonstop, when using MQGMO_SET_SIGNAL with WebSphere
  MQ dynamic queues, if the  MQCLOSE/MQCO_DELETE_PURGE
  operation is performed with an outstanding signal (
  that is, before a signal was received or it timed out)
  the queue is not deleted. If the MQGMO_SET_SIGNAL option
  is not used, the queues will be deleted as expected.
  

Local fix

• Do not use MQGMO_SET_SIGNAL GMO when doing MQGETs on
  dynamic queues.
  

Problem summary

• If an application opens a model queue and then posts an MQGET
  with MQGMO_SET_SIGNAL against it,  if the queue is closed with
  MQCO_DELETE or MQCO_DELETE_PURGE,  the following set of FDCs are
  produced.
  QS074001 from qslUnloadQueue
  QS072003 from qslHandleDelete
  QS164001 from qslMapHandle
  QS191000 from qslHandleClose
  KN070001 from kqiDeleteQPath
  This is a result of the object delete logic in the queue server
  not handling the case where there are outstanding waiters
  at the time an object is deleted
  

Problem conclusion

• If tbe object being deleted is a dynamic queue, it is not an
  error to delete it with outstanding MQGET with MQGMO_SET_SIGNAL.
  The queue server object delete logic should cancel the waiter(s)
  and then delete the object.
  

Temporary fix

• Terminate the application that originally posted the MQGET with
  MQGMO_SET_SIGNAL, then delete the orphaned object manually.
  

Comments

APAR Information

• 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

  WEBS MQ NSS ITA

• Fixed component ID

  5724A3902

Applicable component levels