1 Reply Latest reply on Apr 18, 2012 6:21 AM by Arunbodap-Oracle

    Nodemanager Issue: Unable to start Managed Server using nmStart()

      Hi Everyone,

      Please help me in resolving the below issue:

      After successfully starting the Admin server of a domain(wd01) using nodemanager nmStart(), i have tried to start the manager server of the same domain using nmStart(), but the server start failed due nodemanager trying to boot the managed server as an admin server, below is the error

      <Apr 17, 2012 11:26:21 AM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

      There are 1 nested errors:

      weblogic.management.ManagementException: Booting as admin server, but servername, ms02, 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:802)
      at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:489)
      at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
      at weblogic.Server.main(Server.java:67)

      <Apr 17, 2012 11:26:21 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>

      I have used the below commands
      1.) nmStart('AdminServer',props=prps)
      2.) nmStart('ms02',props=prps)

      Defined the properties as mentioned below
      arg = "Arguments=\" -server -Xms128m -Xmx512m -XX:MaxPermSize=256m \""
      prps = makePropertiesObject (arg)
      nmStart('AdminServer', props=prps)

      Thanks in Advance,
        • 1. Re: Nodemanager Issue: Unable to start Managed Server using nmStart()
          nmStart will look for boot.properties and startup.properties files when trying to start a managed server. If it does not find these files, it will assume that it is starting an Admin Server.
          Also, even if these files are manually created, nmStart would start the managed server in MSI (Managed Server Independence) mode.
          So, WebLogic recommends starting the managed servers using the "start" WLST command instead of "nmStart" command.
          "Using the start command causes WLST to contact the Administration Server to determine the Managed Servers startup properties. These are in turn passed to Node Manager and are used to start the Managed Server."
          Thus, the managed server will still be monitored by the node manager.

          "The following general procedures are recommended for starting a Managed Server using WLST and Node Manager.
          1. Start Node Manager. See Starting Node Manager.
          2. Start an Administration Server. See Starting Instances of WebLogic Server in Managing Server Startup and Shutdown.
          3. Invoke WLST and connect to an Administration Server using the connect command.
          4. Start your Managed Server using the WLST start command."

          For further information, review the following documentation:

          So, please do not use nmStart to start your managed server expecially when you are starting for the first time.
          Start the managed server using the "start" WLST command as explained in the above steps (picked from documentation)

          1 person found this helpful