PI26843: RESOLVE MULTIPLE COLLECTIVE MEMBER TESTS FAILURE PROBLEMS

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

• This APAR addresses the following Collective member issues:
  .
  1. An AccessControlException is thrown when re-registering a
  member that was removed from the Collective and marked as
  disconnected.
  .
  2. The install directory was not set correctly when publishing
  the Collective member path.
  .
  3. An "IllegalThreadStateException: Thread is already started"
  error was thrown when publishing the collective member data to
  the repository
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Resolve multiple WebSphere collective   *
  *                      member problems                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR has resolved the following WebSphere collective member
  problems:  1. An AccessControlException was thrown when re-
  registering a member that was removed from the Collective.  2.
  The installDir was not set correctly when publishing the
  Collective member path.  3. An IllegalThreadStateException was
  thrown when publishing collective member data to the repository
  

Problem conclusion

• There are bugs in the Collective member when re-registering a
  member after it was removed from Collective and the InstallDir
  was also not set correctly when publishing the Collective member
  path. These problems have now been resolved.  The fix for this
  APAR is currently targeted for inclusion in fix pack 8.5.5.4.
  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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP