PI46378: Collective and cluster member started/stopped state not promptly updated.

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

• Collective and cluster server members running state (STARTED
  or STOPPED) is tracked in the collective controller and
  events are generated when the state changes. In some cases
  the state change and or event generation may take a long
  time or (rarely) may not occur at all.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile - Systems Management *
  *                  Functions                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Collective and cluster member started   *
  *                      and stopped state is not promptly       *
  *                      updated.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This issue affects STATE change events for collective member
  servers.  In some cases, when stopping  a collective member
  server, the state change event  (STOPPED) may not be generated
  for a long time or very rarely, may not occur at all.
  

Problem conclusion

• The code was modified to promptly generate a state change event
  when a collective member server is shutdown.
  
  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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP