PI54179: Failure to assign a unique port value to a newly created cluster member

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

• WebSphere Application Server 8.5.5.3 Network Deployment edition.
  Linux Operating System.
  
  The customer is running into an issue of "Port conflict"
  when they creates multiple clusters using a custom script.
  The problem is intermittent.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5, Network Deployment edition.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Newly created cluster member may        *
  *                      receive port values of ports already    *
  *                      in use                                  *
  ****************************************************************
  * RECOMMENDATION:  Apply the FixPack containing this APAR.     *
  ****************************************************************
  When creating cluster members, we may fail to assign a unique
  port value to the cluster member, resulting in a port conflict
  (duplicate port with a port already used by the WebSphere
  Application Server installation).
  

Problem conclusion

• Code has been corrected so that a unique port will be
  assigned.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.10.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP