IV51059: PROBE ID XC307009 FROM XLSREQUESTMUTEXSEM AS SEMAPHORE EYECATCHER IS CORRUPT

WebSphere MQ V7.0 Fix Pack 7.0.1.12
Fix Pack 7.1.0.5 for WebSphere MQ V7.1
WebSphere MQ V7.5 Fix Pack 7.5.0.4

APAR status

• Closed as program error.

Error description

• An FDC with Probe Id XC307009 is generated because a semaphore
  eyecatcher is bad. Trace data in the FDC includes :
  
  { zlaProcessMessage
  -{ zlaProcessMQIRequest
  --{ zlaMQGETM
  ---{ zcpCreateMessage
  ---} zcpCreateMessage rc=OK
  ---{ zsqMQGETM
  ----{ kpiMQGETM
  -----{ kqiQPathCheckAndSet
  -----} kqiQPathCheckAndSet rc=MQRC_Q_DELETED
  ----} kpiMQGETM rc=OK
  ---} zsqMQGETM rc=MQRC_Q_DELETED
  --} zlaMQGETM rc=MQRC_Q_DELETED
  --{ zcpDeleteMessage
  --} zcpDeleteMessage rc=OK
  --{ zcpSendOnPipe
  ---{ xcsResetEventSem
  ---} xcsResetEventSem rc=OK
  ---{ xcsPostEventSem
  ----{ xlsLockEvent
  ----} xlsLockEvent rc=OK
  ----{ xlsUnlockEvent
  ----} xlsUnlockEvent rc=OK
  ---} xcsPostEventSem rc=OK
  --} zcpSendOnPipe rc=OK
  -} zlaProcessMQIRequest rc=OK
  } zlaProcessMessage rc=OK
  { zcpReceiveOnPipe
  -{ xcsWaitEventSem
  --{ xlsLockEvent
  --} xlsLockEvent rc=OK
  --{ xlsUnlockEvent
  --} xlsUnlockEvent rc=OK
  -} xcsWaitEventSem rc=OK
  } zcpReceiveOnPipe rc=OK
  { zlaCheckStatus
  } zlaCheckStatus rc=OK
  { zlaProcessMessage
  -{ zlaProcessMQIRequest
  --{ zlaMQCB
  ---{ zcpCreateMessage
  ---} zcpCreateMessage rc=OK
  ---{ zsqMQCB
  Data: 0x00020000
  ----{ zsqVerifyQueueObj
  -----{ zsqVerifyObj
  -----} zsqVerifyObj rc=OK
  ----} zsqVerifyQueueObj rc=OK
  ----{ kpiMQCB
  -----{ kqiRegisterConsumer
  ------{ xlsRequestMutex
  -------{ xcsBuildDumpPtr
  --------{ xcsGetMemFn
  --------} xcsGetMemFn rc=OK
  -------} xcsBuildDumpPtr rc=OK
  -------{ xcsFFST
  
  and this indicates that the problem occurs during asynchronous
  consumer registration.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  You may be impacted by this problem if you have a system
  utilizing the MQ asynchronous consume facility and the queue
  concerned is deleted whilst messages are being consumed from it.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows)
  ****************************************************************
  PROBLEM SUMMARY:
  The asynchronous consume function that gets messages off a queue
  detected, at an early stage of its processing, that a queue was
  deleted. However, it failed to ensure that any subsequent
  callback would know that the queue had been deleted. A
  subsequent callback could then incorrectly access aspects of the
  queue which had been deleted.
  

Problem conclusion

• Ensured that the asynchronous consume function that gets
  messages off a queue, if it detected a deleted queue, correctly
  recorded that for any subsequent callback.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.1.12
  v7.1       7.1.0.5
  v7.5       7.5.0.4
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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:

Fix information

• Fixed component name

  WMQ AIX V7

• Fixed component ID

  5724H7221

Applicable component levels

• R701 PSY

     UP