PI53301: DELAY OBSERVED WHEN CONSUMING MESSAGES FROM A V8.5.5 SIB DESTINATION

8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• In Websphere v8.5.5 clustered Service Integration Bus (SIB)
  topology with 2 messaging engines configured and message
  producer and consumer applications deployed onto the same
  cluster, considerable delay is observed while consuming the
  messages from the destination.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider     *
  *                  for IBM WebSphere Application Server V8.5.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: A Message Driven Bean (MDB) is not      *
  *                      consuming a message as soon as the      *
  *                      message is produced by the message      *
  *                      producer.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem is applicable for non-persistent messages where
  batching will happen and the message production rate is slow.
  This makes the batch not be commited until the batch
  completion. Message(s) are not available for an MDB or any
  other message consumer for consumption until the message is
  comitted into the message store.
  Trace shows the delay in batch completion.
  BatchHandler  >  messagesAdded
  (...delay observed in between..)
  BatchHandler  >  completeBatch
  Message(s) in batch can be commited only when the batch gets
  full (or) the Alarm triggers. The Alarm is not triggered
  because the previous Alarm is still incomplete due to
  redeundant "AIRequestedTick" objects in the list and all of
  them are processed. It is expected to communicate to the
  remote messaging engine (ME) when processing each
  "AIRequestedTick".
  

Problem conclusion

• Source code has been fixed to avoid storing redeundant
  "AIRequestedTicks" in the list.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.10.  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

  WAS SIB & SIBWS

• Fixed component ID

  620800101

Applicable component levels

• R850 PSY

     UP