PH31182: LOOP WHEN TRYING TO DELETE THE FIRST MESSAGE IN THE QUEUE.

APAR status

• Closed as program error.

Error description

• SIBus JMS destinations accumulate expired messages.
  The expirer is looping trying to delete the first message in
  the queue. This behaviour is brought about because the first
  message appears to be locked in a long running internal
  transaction.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The message expiry processor fails, so  *
  *                      expired messages accumulate.            *
  *                      FFDC:                                   *
  *                      com.ibm.ws.sib.msgstore.gbs.OptimisticD *
  *                      ep                                      *
  *                      thException                             *
  ****************************************************************
  * RECOMMENDATION:  This problem is unlikely to recur after the *
  *                  message processor has been stopped and      *
  *                  restarted. If it does apply the fix.        *
  ****************************************************************
  The following stack trace will be seen in a n FFDC.
  Exception:com.ibm.ws.sib.msgstore.MessageStoreRuntimeException
  SourceId:com.ibm.ejs.util.am._Alarm.run ProbeId:95
  Reporter:com.ibm.ejs.util.am._Alarm@2620b3b3
  com.ibm.ws.sib.msgstore.MessageStoreRuntimeException:
  CWSIS2001E: The expiry daemon ended abnormally due to an
  unexpected exception:
  com.ibm.ws.sib.msgstore.gbs.OptimisticDepthException:
  maxDepth(47) exceeded. Depth is 48.
  at
  com.ibm.ws.sib.msgstore.expiry.Expirer.alarm(Expirer.java:598)
  at com.ibm.ejs.util.am._Alarm.runImpl(_Alarm.java:151)
  at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:136)
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)
  Caused by:
  com.ibm.ws.sib.msgstore.gbs.OptimisticDepthException:
  maxDepth (47) exceeded. Depth is 48. at
  com.ibm.ws.sib.msgstore.gbs.NodeStack.push(NodeStack.java:155)
  at
  com.ibm.ws.sib.msgstore.gbs.NodeStack.push(NodeStack.java:143)
  at
  com.ibm.ws.sib.msgstore.gbs.GBSIterator.nextNode(GBSIterator.ja
  va:704)
  at
  com.ibm.ws.sib.msgstore.gbs.GBSIterator.internalGetNext(GBSIter
  ator.java:656)
  at
  com.ibm.ws.sib.msgstore.gbs.GBSIterator.pessimisticGetNext(GBSI
  terator.java:613)
  at
  com.ibm.ws.sib.msgstore.gbs.GBSIterator.findNextBeforeEof(GBSIt
  erator.java:411)
  at
  com.ibm.ws.sib.msgstore.gbs.GBSIterator.findNext(GBSIterator.ja
  va:381)
  at
  com.ibm.ws.sib.msgstore.gbs.GBSIterator.next(GBSIterator.java:7
  51)
  at
  com.ibm.ws.sib.msgstore.expiry.ExpiryIndex.next(ExpiryIndex.jav
  a:151)
  at
  com.ibm.ws.sib.msgstore.expiry.Expirer.alarm(Expirer.java:526)
  

Problem conclusion

• The fix for this APAR is targeted for inclusion in fix packs
  8.5.5.20 and 9.0.5.8. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP