PI41759: CLUSTER RIPPLESTART DELAYS WHEN ATTEMPTED FROM STOPPED OR STARTE D STATE

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.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

• Depending on the state from which a ripplestart is attempted,
  the cluster start process can be delayed. This is caused by
  delays on running launch and stop member processes because of
  improperly handlded member status notifications.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using Ripple Start to start or       *
  *                  cycle clusters                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When attempting to ripple start a       *
  *                      cluster there is a delay in cluster     *
  *                      state transitioning from partially      *
  *                      started to started                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Depending on what state a cluster is ripple started from
  (started state or stopped state) the ripple start process can
  hit conditions in which there is a delay in processing the
  respective launchMember or stopMember notification. In
  addition to the state a cluster is ripple started from,
  attempting ripple start on a single member cluster can also
  lead to a condition in which there is a delay in processing
  the corresponding start notification.
  In either of these cases if the notification is not handled
  properly, the cluster state will remain in partially started
  state until the ripple start notification timeout triggers,
  and cluster states are updated as expected.
  

Problem conclusion

• A fix was made to the ripple start process in the workload
  management (WLM) Cluster Mbean to ensure launch member and
  stop member notifications are properly handled from both
  stopped and started states for single member and multiple
  member clusters.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.7.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP