IBM Support

WebSphere Application Server migration assignment of port numbers to new endpoint addresses can cause port conflicts

Troubleshooting


Problem

When migrating federated nodes, the migration tools might select a reserved port and assign it to a new endpoint address. This results in port conflicts, which cause your environment to function improperly.

Symptom

You might see the following error in the log file:

BBOO0220E: ODCF8005E: There was an unexpected exception while initializing the SON overlay; the exception is java.io.IOException: The P2P layer was unable to bind to a UDP port.

Resolving The Problem

After migration is complete, edit the serverindex.xml file and change any conflicting port assignments.

On z/OS, you can find the port range settings in the BPXPRMxx parmlib member, which contains parameters that control the z/OS UNIX System Services environment and the file systems. For example:

FILESYSTYPE TYPE(CINET) ENTRYPOINT(BPXTCINT)
NETWORK DOMAINNAME(AF_INET)

    DOMAINNUMBER(2)
    MAXSOCKETS(64000)
    TYPE(CINET)
      INADDRANYPORT(30000)
      INADDRANYCOUNT(4000)

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Migration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.5.5;8.5;8.0;7.0;6.1","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Migration","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"8.5.5;8.5;8.0;7.0;6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21643769