Sunday, October 25, 2015

Unable to start Node Manager due to Port/Address bind exception:


Unable to start Node Manager Process due to Port/Address bind exception.


weblogic.nodemanager.server.NMServer main SEVERE: Fatal error in node manager server Address already in use at Method) at at at<init>( at<init>( at weblogic.nodemanager.server.Listener.init( at weblogic.nodemanager.server.NMServer.start( at weblogic.nodemanager.server.NMServer.main( at weblogic.NodeManager.main(


Port configured for Node Manager is already in use. 
This is because another application is using the port configured for Node Manager, so that when Node Manager tries to bind to the port, it is not able to start and fails with above error.


Please follow below instructions to change the port number of your Node Manager configuration: 

Step 1) Go to below mentioned location

Step 2) Take backup of files
$cp nodemanager.properties_BKP 

Step 3) Change ListenPort=XXXX parameter to an available port.
netstat -an | grep Portnumber
Eg: netstat -an | grep 5557
-->If no output then port is free and avaliable for use. 

Step 4) Save it. 

Step 5) Start the Node manager Process as below:
$nohup ./ & 

Step 6) We will then have to configure the new Node Manager port (Set in Step 3) in the Machines section of the WebLogic Server console for it to be known to the Administration Server.

Note :
If you don't find in that location, that means you haven't started nodemanager atleast once and hence file is not generated. Hence start nodemanager, using the script located in  $WL_HOME/server/bin/

No comments:

Post a Comment

Other Posts