PM25272: MESSAGES SUCCESSFULLY CONSUMED FROM AN SERVICE INTEGRATION BUS DESTINATION ARE NOT REMOVED FROM THE SIB001 DATABASE TABLE.

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 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

• An Application sends messages to a WebSphere Service Integration
  Bus(SIB) destination. The consumer application successfully
  consumes messages from the destination. However the message
  store table SIB001 keeps growing even though there are no
  messages on the SIB destinations.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider     *
  *                  for IBM WebSphere Application Server V6.1   *
  *                  and V7                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The SIB001 table grows in size even     *
  *                      though messages are successfully        *
  *                      consumed and the Service Integration    *
  *                      Bus destinations contain no messages.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The SIB001 table holds persistent messages for the destinations
  defined on the Service Integration Bus (SIB). Even though
  messages are successfully consumed and no (or few) messages
  exist on the destinations, the size of the SIB001 table
  contains many rows (100+).
  
  The problem was caused by a timing window where a Reliable
  Persistent message was committed to a destination at the same
  time as a message was consumed from a destination. This timing
  window means that only a small percentage of messages will be
  incorrectly left in the SIB001 table following successful
  consumption.
  
  This problem only effects applications that both consume and
  produce messages in the same transaction to the same messaging
  engine (i.e. an MDB that also sends a message to the same
  messaging engine). The message that is sent must have a
  reliability of 'Reliable Persistent'.
  

Problem conclusion

• This APAR fixes the problem. Messages built up before this
  APAR is applied will not be removed and will require manual
  removal from the database.
  
  To remove the correct entries from the SIB001 table do the
  following:
  1) Stop the messaging engine that is running against the
  database.
  2) Ensure that the SIBXACTS table is empty. If not restart the
  messaging engine and make sure all transactions are resolved.
  3) Remove all rows from the SIB001 table that contain '1' in
  the 'DELETED' column.
  4) Restart the messaging engine.
  
  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

• Remove the messages built up in the SIB001 table by following
  the steps in the 'Problem Conclusion' section.
  

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

  620600101

Applicable component levels

• R200 PSY

     UP