Oct 152012

When we start the managed server with the help of nmStart() we might see the following unusual error in NodeManager logs

NMProcess: java.io.IOException: Server failed to start up. See server output log for more details.
NMProcess: at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
NMProcess: at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
NMProcess: at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:71)
NMProcess: at java.lang.Thread.run(Thread.java:662)
Error Starting server mgs1: weblogic.nodemanager.NMException: Exception while starting server 'managedserver1'

In Server StdOut File Shows below log entries :

<Jun 23, 2012 11:50:27 PM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Jun 23, 2012 11:50:28 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsystems Inc.>
<Jun 23, 2012 11:50:29 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Tue Nov 15 08:52:36 PST 2011 1441050 >
<Jun 23, 2012 11:50:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.management.ManagementException: Booting as admin server, but servername, managedserver1, does not match the admin server name, AdminServer
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)

<Jun 23, 2012 11:50:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 23, 2012 11:50:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 23, 2012 11:50:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jun 23, 2012 11:50:30 PM> <FINEST> <NodeManager> <Waiting for the process to die: 252>
<Jun 23, 2012 11:50:30 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
Above exception generally comes when you have specified the nodemanager home elsewhere from the default place (%WL_HOME%/common/nodemanager)
When started with nmStart() from wlst, for which nodemanager home is established outside the WL_HOME directory, managed server/node manager is not really aware of the Admin Server Information (It’s Running or Dead), We need to inform the Node Manager that the server it’s starting is the Managed Server and there is Admin Server exists for this server to manage or not.


Please follow below steps to fix this issue:

– Create the Node Manager and Set the Node Manager Home to Different Directory in startNodeManager.cmd (can be set in startNodeManager.sh file) in %WL_Home%/server/bin

call "%WL_HOME%\common\bin\commEnv.cmd"

@REM set NODEMGR_HOME=%WL_HOME%\common\nodemanager

set NODEMGR_HOME=F:\NodeManager

– Create the Folder and copy few files which are required for the basic nodemanager setup as below :


– Start the Node Manager with %WL_HOME%/server/bin/startNodeManager.cmd localhost 5555 (Which is the Nodemanger configured at the WebLogic Server Console for the Server Instances)


<Jul 2, 2012 5:30:22 PM> <INFO> <Loading domains file: F:\NodeManager\nodemanager.domains>
Jul 2, 2012 5:30:22 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap

INFO: Loading domains file: F:\NodeManager\nodemanager.domains
<Jul 2, 2012 5:30:23 PM> <INFO> <Loaded node manager configuration properties from 'D:\NODEMA~1\nodemanager.properties'>
Jul 2, 2012 5:30:23 PM weblogic.nodemanager.server.NMServer <init>
INFO: Loaded node manager configuration properties from 'D:\NODEMA~1\nodemanager.properties'Node manager v10.3

Configuration settings:


Domain name mappings:

NodeManagerDomain -> F:\Oracle\Middleware\WebLogic Server\\user_projects\domains\NodeManagerDomain<Jul 2, 2012 5:30:25 PM> <INFO> <NodeManagerDomain> <managedserver1> <Startup configuration properties loaded from "F:\Oracle\Middleware\WebLogic Server\\user_pro
Jul 2, 2012 5:30:25 PM weblogic.nodemanager.server.AbstractServerManager log
INFO: Startup configuration properties loaded from "F:\Oracle\Middleware\WebLogic Server\\user_projects\domains\NodeManagerDomain\servers\managedserver1\data\nodemanager\startup.properties"
<Jul 2, 2012 5:30:25 PM> <INFO> <NodeManagerDomain> <managedserver2> <Startup configuration properties loaded from "F:\Oracle\Middleware\WebLogic Server\\user_pro
Jul 2, 2012 5:30:25 PM weblogic.nodemanager.server.AbstractServerManager log
INFO: Startup configuration properties loaded from "F:\Oracle\Middleware\WebLogic Server\\user_projects\domains\NodeManagerDomain\servers\managedserver2\data\nodemanager\startup.properties"
<Jul 2, 2012 5:30:25 PM> <INFO> <Plain socket listener started on port 5555, host localhost>
Jul 2, 2012 5:30:25 PM weblogic.nodemanager.server.Listener run
INFO: Plain socket listener started on port 5555, host localhost

– Once you enroll the nodemanager by nmEnroll(), you will see that there are other files and directories gets created in the D:/NodeManager Directory as below :

bin – scripts for service migration and server migration
config – nodemanager – nm_password.properties
security – SerializedSystemIni.dat

– Make sure the managed server should have following files to start the server with Node Manager

<DOMAIN_HOME>/servers/mgserver/data/nodemanager/boot.properties (which should have username and password to start the WebLogic Server.
<DOMAIN_HOME>/servers/mgserver/data/nodemanager/startup.properties – which should contain below parameters


– Specify the below URL at Arguments Section of Managed Server’s Server Start Tab


(Admin Server URL)

Restart the servers.
– Start WLST and Start the Server with nmStart()

F:\Oracle\Middleware\WebLogic Server\\wlserver_10.3\common\bin>wlst.cmd

Initializing WebLogic Scripting Tool (WLST) …

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

We can start the node manager with following command too.

wls:/offline> startNodeManager(verbose='true',NodeManagerHome='F:\NodeManager',
Launching NodeManager ...
Start The Admin Server to Enroll the Node Manager by StartWebLogic.sh And Enroll the NodeManager as below.

wls:/offline> nmEnroll('F:\Oracle\Middleware\WebLogic Server\\user_projects\domains\NodeManagerDomain','F:\NodeManager')
Once Enrolled Connect to the Running Node Manager - You will see the files in Step 4 Getting created in the D:/NodeManager Directory

nmConnect('weblogic','weblogic123','localhost','5555','NodeManagerDomain','D:/Oracle/Middleware/Weblogic Server/','plain')
Connecting to Node Manager ...
Successfully Connected to Node Manager.
Once Connected you can start the Admin And Managed Servers as below if they are configured to start from the Node Manager.

wls:/nm/NodeManagerDomain> nmStart('AdminServer')
Starting server AdminServer ...
Successfully started server AdminServer ...

wls:/nm/NodeManagerDomain> nmStart('managedserver1')
Starting server managedserver1 ...
Successfully started server managedserver1 ...

Note : As Noted earlier, you no need to have Admin Server RUNNING to start the Managed Server from nmStart() command.



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

  2 Responses to “How to Fix nmStart() fails to start server Error | Weblogic”

  1. i ma unable to start managed server using nodemanager
    I have a weblogic cluster containing 1 admin server and two managed servers.

    whenever i try to start managed server using nmStart i get following error
    <Unable to establish JMX connectivity with the Administration Server AdminServer at service:jmx:t3://[2001:0:9d38:6ab8:46c:3c5e:f573:ee98]:7001/jndi/weblogic.management.mbeanservers.domainruntime.
    at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
    at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
    at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    at weblogic.management.mbeanservers.runtime.internal.RegisterWithDomainRuntimeService.getDomainMBeanServerConnection(RegisterWithDomainRuntimeService.java:222)
    Truncated. see log file for complete stacktrace

    plse help me

    • The “Domain Runtime” MBeanServer. It aggregates the MBeans registered on the domain’s “Runtime” MBeanServers. So as long as a managed server is up, its MBeans can be accessed through the “Domain Runtime” MBeanServer. To connect to that MBeanServer, just use the following JMX URI:


      The code must be something like so the hostname should be some valid hostname FQDN or host IP address to make nmstart work:
      JMXServiceURL serviceUrl =
      new JMXServiceURL(

      Change your host name from 2001:0:9d38:6ab8:46c:3c5e:f573:ee98 to actual FQDN or the host IP address of weblogic admin server in “nodemanager.properties” and config.xml file and try to start the server again using nmstart.

Leave a Reply

Show Buttons
Hide Buttons