PM27294: MESSAGE EXPIRATION STOPS AND MESSAGES BUILD UP ON DESTINATIONS

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Expiration of message in the Service Integration Bus may stop
  and expired messages build up on destinations.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider for *
  *                  IBM WebSphere Application Server            *
  ****************************************************************
  * PROBLEM DESCRIPTION: The expiration of messages stops and    *
  *                      as a result, messages that should have  *
  *                      expired begin to build up on queue.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A problem with the message expiration logic caused the thread
  responsible for expiring messages to terminate.  Therefore,
  messages that had expired were not being deleted from
  destinations and would accumulate.  The problem that caused
  the termination was recorded in an FFDC:
  
  Exception:com.ibm.websphere.sib.exception.SIIncorrectCallExcepti
  on SourceId:com.ibm.ws.sib.msgstore.expiry.Expirer.run
  ProbeId:441
  Reporter:com.ibm.ws.sib.msgstore.expiry.Expirer@xxxxxxxx
  com.ibm.websphere.sib.exception.SIIncorrectCallException:
  CWSIS1004E: The transaction cannot be committed. The
  transaction is complete or completing.
  at
  com.ibm.ws.sib.msgstore.transactions.MSDelegatingLocalTransactio
  n.commit(MSDelegatingLocalTransaction.java:342)
  at
  com.ibm.ws.sib.msgstore.expiry.Expirer.alarm(Expirer.java:539)
  at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:127)
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
  
  This Exception was caused by a small timing window in which two
  different alarms could be scheduled to run the Expirer thread,
  and if these two threads ran concurrently then the above
  Exception is possible.
  
  Other RuntimeExceptions could also cause the Expirer thread to
  terminate.
  
  NOTE - no expired messages will be delivered to consumers when
  this problem occurs.  The problem only causes unconsumed and
  expired messages to remain on the destination.
  

Problem conclusion

• This APAR prevents the concurrent scheduling and execution of
  threads for the Expirer, and also prevents any runtime
  exceptions from terminating the Expirer.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.17.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  PLAT MSG COM

• Fixed component ID

  620800101

Applicable component levels

• R300 PSY

     UP