May 112012
 Posted by on May 11, 2012 at 8:05 am Application Servers, Java App Servers, Oracle/BEA WebLogic Tagged with:  Add comments


SOA Installed on top of WLS 10.3.

Started weblogic admin Server and executed startNodeManger.cmd.


Nodemanger Error

Nodemanger description log

In command prompt showing the listener started on port 5556 as given below:

<Jul 19, 2011 4:18:59 PM> <INFO> <Secure socket listener started on port 5556>

<Jul 19, 2011 4:18:59 PM weblogic.nodemanager.server.SSLListener run

INFO: Secure socket listener started on port 5556

In the nodemanager.log file also showing the same result:

<Jul 19, 2011 4:18:56 PM> <INFO> <Loading domains file: D:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\>

<Jul 19, 2011 4:18:58 PM> <INFO> <Loading identity key store: FileName=D:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>

<Jul 19, 2011 4:18:58 PM> <INFO> <Loaded node manager configuration properties from 'D:\Oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\'>

<Jul 19, 2011 4:18:59 PM> <INFO> <Secure socket listener started on port 5556>

I see in weblogic server console the status of Node Manager is showing inactive and

problem description is, and the Message is ‘GETNMLOG’ not applicable to scripted nodemanager.

To resolve this follow below steps:

Check the NodeManager listen address in the admin console and make sure your NM process is using it.

Check your Domain is configured to talk to remote machines via SSH nodemanager, If yes go for below steps:

If you are running Java node manager on your host machines – You need to change the value in the “Type” to “SSL” from “SSH” drop down box field in the console and need to restart it to show proper ACTIVE state in WL console.


© Incase of any copyright infringements please check copyrights page for faster resolutions.

Leave a Reply

Show Buttons
Hide Buttons