PM94584: ADDING A NODE TO A NODEGROUP IN A DYNAMIC CLUSTER THE NEWLY CREATED CLUSTER MEMBERS DO NOT FOLLOW THE PORT TEMPLATE

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
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

APAR status

• Closed as program error.

Error description

• When adding a node to a nodegroup which is used to define a
  dynamic cluster's membership policy the newly created DC members
  will not follow the cluster template when assigning the new
  cluster member's ports.
  

Local fix

• Manually alter the ports for the new cluster members
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a dynamic cluster membership       *
  *                      policy has new nodes, not all           *
  *                      properties are propagated.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a dynamic cluster membership policy has new nodes, not
  all properties are propagated. This is an intermittent issue
  based on timing.
  

Problem conclusion

• The code was updated to propagate all dynamic cluster
  properties in an iterative manner which will prevent timing
  issues.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.1.  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