Fatal error in node manager server java.net.BindException: Address already in use during startNodeManager.sh in Weblogic

Hi,

When I start Weblogic Server, I got ” Fatal error in node manager server java.net.BindException: Address already in use ” error while starting Node Manager.

When I try to start up Weblogic Server after Server reboot, Node manager is not started and failed with following errors.

[oracle@MehmetSalih ]$ nohup /u01/app/oracle/middleware/wlserver_10.3/server/bin/startNodeManager.sh &

<Jul 23, 2019 11:48:29 AM> <SEVERE> <Fatal error in node manager server>
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
at java.net.ServerSocket.bind(ServerSocket.java:376)
at javax.net.ssl.impl.SSLServerSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at java.net.ServerSocket.<init>(ServerSocket.java:181)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:136)
at javax.net.ssl.impl.SSLServerSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source)
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:76)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:382)
at weblogic.NodeManager.main(NodeManager.java:31)

Jul 23, 2019 11:48:29 AM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)

This means one of the Linux process is holding Nodemanager Process, so We are taking ” java.net.BindException: Address already in use “.

To solve this problem you need to kill this process like following.

Port of NodeManager is 5560, so find related process PID like following.

[oracle@MehmetSalih nodemanager]$ netstat -tulpn | grep 5560
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 :::5560                     :::*                        LISTEN      27910/java
[oracle@MehmetSalih nodemanager]$

Kill this process and check it again.

[oracle@MehmetSalih nodemanager]$ kill -9 27910
[oracle@MehmetSalih nodemanager]$
[oracle@MehmetSalih nodemanager]$
[oracle@MehmetSalih nodemanager]$ netstat -tulpn | grep 5560
(No info could be read for "-p": geteuid()=54323 but you should be root.)
[oracle@MehmetSalih nodemanager]$

After killing related process, Node Manager is started successfully with following script.

[oracle@MehmetSalih ]$ nohup /u01/app/oracle/middleware/wlserver_10.3/server/bin/startNodeManager.sh &