PI41998: IN WAS 8.5, MANUAL REENABLEMENT OF MESSAGING ENGINE FAILS AFTER IT IS AUTOMATICALLY PROBED TO ENABLE FOR 5 TIMES

APAR status

• Closed as program error.

Error description

• In WAS 8.5, manual reenablement of messaging engine fails after
  it is automatically probed to enable for 5 times
  ************************************************
  THIS APAR IS APPLICABLE TO WAS 8.5 ONLY
  ************************************************
  We observe the following exception in logs:
  
  [5/28/15 2:36:12:890 PDT] 00000252 SibMessage    E
  [BPM.ProcessCenter.Bus:SingleCluster.000-BPM.ProcessCenter.Bus]
  CWSID0027E: Messaging engine
  SingleCluster.000-BPM.ProcessCenter.Bus
  cannot be restarted because a serious error has been reported.
  
  [5/28/15 2:36:12:890 PDT] 00000252 SibMessage    E
  [BPM.ProcessCenter.Bus:SingleCluster.000-BPM.ProcessCenter.Bus]
  CWSID0054E: Messaging engine
  SingleCluster.000-BPM.ProcessCenter.Bus is
  not enabled, as the re-enable count 5 exceeded.
  
  The ME- reenable feature attempts to reenable the messaging
  engine for 5 times and if the messaging engine cannot start
  even after 5 attempts, the messaging engine would be disabled.
  In the customer scenario, we observe that 5 attempts were made
  to start the messaging engine but it failed, so the messaging
  engine was disabled.
  
  Later when the messaging engine was manually attempted to
  re-enable, we check for the re-enable count, if it exceeds 5,
  we throw the above exception and fail to start the messaging
  engine. Since in the customer scenario, the retry count has
  reached 5 already, the messaging engine is not started.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider     *
  *                  for                                         *
  *                  IBM WebSphere Application Server            *
  ****************************************************************
  * PROBLEM DESCRIPTION: In WebSphere Application Server         *
  *                      version 8.5, manual reenablement of     *
  *                      messaging engine (ME) fails after it    *
  *                      is disabled and automatically probed    *
  *                      to enable 5 times.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In WebSphere Application Server version 8.5, ME reenable
  feature attempts to reenable the disabled messaging engine
  5 times and if the messaging engine cannot start after 5
  attempts, the ME would be disabled. It could be reenabled
  manually through the administrative console.
  However, in V8.5, when the messaging engine is attempted to
  be re-enabled manually through the console, the messaging
  engine fails to start and we observe following exception in
  the logs -
  CWSID0054E: Messaging engine
  SingleCluster.000-BPM.ProcessCenter.Bus is not enabled, as the
  re-enable count 5 exceeded.
  

Problem conclusion

• When the messaging engine is attempted to re-enable through the
  administrative console, the re-enable count is checked and
  since it has reached its default maximum(which is 5), the
  request to enable the messaging engine is not honored. So, the
  solution is to reset the re-enable count after all the 5
  attempts to enable the messaging engine fails so that manual
  reenablement is honored.
  
  Note: This problem is already corrected in V8.5.5 and higher.
  This APAR delivers an interim fix for V8.5.0.2.
  

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