PI10877: MESSAGES ARE NOT CONSUMED AFTER RESTART OF MESSAGING ENGINE.

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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 Application Server V8.5, messages are not
  getting consumed from a queue after the messaging engine is
  restartd. Also the following can be observed:
  
  - Before messaging engine restart, messages are getting
  consumed without any issues.
  - This problem cannot be reproduced every time during
  messaging engine restart.
  - When heavy WebSphere Application Server tracing is enabled
  the problem does not occur.
  
  Also the following NullPointerException may be present in an
  FFDC file:
  
  java.lang.NullPointerException
  at
  com.ibm.ws.sib.processor.impl.MessageProcessor.getMessagingEn
  gineUuid(MessageProcessor.java:2960)
  at
  com.ibm.ws.sib.processor.impl.ConnectionImpl.getMeUuid(Connec
  tionImpl.java:3951)
  at
  com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.
  dropConnection(SibRaCommonEndpointActivation.java:1384)
  at
  com.ibm.ws.sib.ra.inbound.impl.SibRaCommonEndpointActivation.mes
  sagingEngineQuiescing(SibRaCommonEndpointActivation.java:1282)
  at
  com.ibm.ws.sib.ra.inbound.impl.SibRaMessagingEngineConnection
  $SibRaConnectionEventThread.executeCallback(SibRaMessagingEngine
  Connection.java:1527)
  ..
  ..
  

Local fix

• Enabling a heavy WAS trace prevents the problem from occuring.
  For example, this trace worked for one customer:
  *=info:SIBJmsRa*:SIBProcessor=all:WAS.j2c=all:RRA=all:Transactio
  n=all:SIBMessageStore=all
  
  This workaround might not work for all environments.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider     *
  *                  for IBM WebSphere Application Server V8.5   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Messages are not getting consumed       *
  *                      after messaging engine (ME) restart.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Messages are not getting consumed after ME restart. Customer
  cannot recreate the problem with tracing enabled. This is
  because of a NullPointerException (NPE) which is caused by a
  timing issue between two threads.
  Thread1 -> Removes ME UUID from all the SIBRa endpoint
  listeners (consumers) listening for the destinations under the
  ME.
  Thread2 -> Stops the ME.
  Thread2 stops the ME and resets the message stopre object to
  "Null" before Thread1 completes. Later Thread1 uses the
  message store object, which causes the NPE.
  

Problem conclusion

• Source code has been added to fix the NullPointerException.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.3. Please refer to the Recommended Updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• This timing issue may disappeare after ME restart especially
  with tracing enabled.
  

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