Middleware

Attempt to Start WebLogic Server Node Manager Fails with "Fatal error in node manager server" java.n

APPLIES TO:

Oracle WebLogic Server - Version 10.0 and later
Information in this document applies to any platform.

SYMPTOMS

This error message is seen when attempting to start the Node Manager service:

<25/06/2012 09:09:46> <Info> <dom1> <adminsvr> <Startup configuration properties loaded from "\data\nodemanager\startup.properties">
<25/06/2012 09:09:48> <SEVERE> <Fatal error in node manager server>
java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method) 
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:141)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:84)
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:72)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:200)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:339)
at weblogic.NodeManager.main(NodeManager.java:31)

Running "netstat -ano" shows that the port we use for Node Manager is in use and listening on a stale PID.

CAUSE

This issue is cased by the failure to specify a listen address in WL_HOME/common/nodemanager/nodemanager.properties.

SOLUTION : To fix this issue, make sure to specify the Listen address

To fix this issue, make sure to specify the Listen address as specified below in the WL_HOME/common/nodemanager/nodemanager.properties file.

ListenAddress=

Make sure to save it. And do the following steps:

Shutdown domain instances including Admin.

Update WL_HOME/common/nodemanager/nodemanager.properties (specify ListenAddress).

Restart the NodeManager.

Startup the admin server.

After the node manager starts, shut it down and restart it to verify the issue has been resolved.

All articles