My Oracle Support Banner

Error "java.io.IOException: The server is unable to create a server socket for listening" Occurs While Starting Node Manager (Doc ID 2514282.1)

Last updated on FEBRUARY 08, 2020

Applies to:

Identity Manager - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

After performing pack/unpack as part of OIM HA setup, the nodemanager startup on OIM Node 2 fails with the following error.

java.io.IOException: The server is unable to create a server socket for listening. The address <Listen_Address> might be incorrect or another process is using port <Port_Number>: java.net.BindException: The socket name is not available on this system. (Bind failed)
at weblogic.nodemanager.server.NMServer$ClassicServer.start(NMServer.java:780)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:362)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:591)
at weblogic.NodeManager.main(NodeManager.java:31)
Caused by: java.net.BindException: The socket name is not available on this system. (Bind failed)
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:417)
at java.net.ServerSocket.bind(ServerSocket.java:444)
at java.net.ServerSocket.(ServerSocket.java:258)
at javax.net.ssl.SSLServerSocket.(SSLServerSocket.java:4)

STEPS
-------

1. Followed OIM HA Guide to propagate configuration changes from OIM Node 1 to Node 2 using pack/unpack scripts.

2. Above Error occurs while starting Node Manager on Node 2.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.