2 Replies Latest reply on Jul 27, 2010 9:15 AM by René van Wijk

    Unable to start managed server using node manager

    717542
      Alright,

      I have drilled enough through this forum, but haven't been able to find a commendable answer to this problem.
      My system has an Admin server and 2 managed servers. My aim is to introduce a new JVM option, for which I do something like this:

      prps=makePropertiesObject('Arguments=-Dmy.Name=abc')
      nmStart('AdminServer', props=prps)
      nmStart('ManagedServer1', props=prps)


      First nmStart goes on successfully but for the second one, it says:
      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:749)
           at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
           at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
           at weblogic.Server.main(Server.java:67)


      Where am I going wrong?

      I've read solutions:
      a) Start wlst.sh from nodemanager directory. Didn't work.
      b) Start managed server for the very first time by startManagerWebLogic.cmd/sh and then by nmStart(). Didn't work.


      Any help is greatly appreciated. Thanks!


      --
      Nitin
        • 1. Re: Unable to start managed server using node manager
          687626
          Since you are passing a cutom properties object I think it is not taking up values for other parameters from startup.properties. Can you try adding your custom arguement in statup.properties in domain_home/servers/ManagedServer1/data/nodeManger folder and don't use wlst properties object.

          Alternatively, you can also try passing AdminURL property in the WLST properties object.
          See this link which has a table which lists all the properties you can pass using a properties object.
          http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/nodemgr_config.html#wp1101026
          • 2. Re: Unable to start managed server using node manager
            René van Wijk
            You can start a managed server as follows:
            print 'START NODE MANAGER';
            startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
            
            print 'CONNECT TO NODE MANAGER';
            nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
            
            print 'START ADMIN SERVER';
            nmStart('AdminServer');
            nmServerStatus('AdminServer');
            
            print 'CONNECT TO ADMIN SERVER';
            connect(adminusername, adminpassword);
            
            print 'START MANAGED SERVER';
            start('VideotheekWebServer','Server');
            nmServerStatus('VideotheekWebServer');
            
            print 'START CLUSTER';
            start('VideotheekCluster','Cluster');
            nmServerStatus('VideotheekServer1');
            nmServerStatus('VideotheekServer2');
            JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).

            The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.