WebSphere Application Server migration assignment of port numbers to new endpoint addresses can cause port conflicts
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.
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)
|Application Servers||WebSphere Application Server for z/OS||Migration||z/OS||8.5.5, 8.5, 8.0, 7.0, 6.1|
More support for:
WebSphere Application Server
Software version: 6.1, 7.0, 8.0, 8.5, 8.5.5
Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS
Software edition: Base, Express, Network Deployment
Reference #: 1643769
Modified date: 2013-08-08