nodeagent...Server launched but failed initialization - Websphere

This is a discussion on nodeagent...Server launched but failed initialization - Websphere ; The addNode command for a secondary node in portal 6 cluster installation ends successfully but the nodeagent faile to initialize When try to start the node agent we receive the same error message startServer.log: ************ ************* End Display Current Environment ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: nodeagent...Server launched but failed initialization

  1. nodeagent...Server launched but failed initialization

    The addNode command for a secondary node in portal 6 cluster installation ends successfully but the nodeagent faile to initialize

    When try to start the node agent we receive the same error message

    startServer.log:
    ************
    ************* End Display Current Environment *************
    [6/5/07 13:19:00:695 AST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
    [6/5/07 13:19:00:966 AST] 0000000a AdminTool A ADMU0128I: Starting tool with the wp_01 profile
    [6/5/07 13:19:00:969 AST] 0000000a AdminTool A ADMU3100I: Reading configuration for server: nodeagent
    [6/5/07 13:19:05:035 AST] 0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
    [6/5/07 13:19:37:178 AST] 0000000a AdminTool A ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in zOS) and other log files under /portal/IBM/WebSphere/AppServer/profiles/wp_01/logs/nodeagent should contain failure information.

    SystemOut.log:
    *************
    [6/5/07 13:19:31:097 AST] 0000000a NameServerImp A NMSV0018I: Name server available on bootstrap port 2809.
    [6/5/07 13:19:31:901 AST] 0000000a UserRegistryI E SECJ0330E: The registry implementation file com.ibm.websphere.wmm.registry.WMMUserRegistry cannot be loaded because of the following exception java.lang.ClassNotFoundException: com.ibm.websphere.wmm.registry.WMMUserRegistry
    at java.net.URLClassLoader$1.run(URLClassLoader.java: 199)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.j ava:187)
    at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtC lassLoader.java:110)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:2 89)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:2 35)
    at java.lang.ClassLoader.loadClassInternal(ClassLoade r.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.ibm.ws.security.registry.UserRegistryImpl.init ialize(UserRegistryImpl.java:198)
    at com.ibm.ws.security.server.SecurityServerImpl.getU serRegistry(SecurityServerImpl.java:481)
    at com.ibm.ws.security.server.SecurityServerImpl.(SecurityServerImpl.java:88)
    at com.ibm.ws.security.server.SecurityServerFactory.c reate(SecurityServerFactory.java:57)
    at com.ibm.ws.security.core.distSecurityComponentImpl .initialize(distSecurityComponentImpl.java:328)
    at com.ibm.ws.security.core.distSecurityComponentImpl .start(distSecurityComponentImpl.java:274)
    at com.ibm.ws.security.core.SecurityComponentImpl.sta rt(SecurityComponentImpl.java:96)
    at com.ibm.ws.runtime.component.ContainerImpl.startCo mponents(ContainerImpl.java:820)
    at com.ibm.ws.runtime.component.ContainerImpl.start(C ontainerImpl.java:649)
    at com.ibm.ws.runtime.component.ServerImpl.start(Serv erImpl.java:408)
    at com.ibm.ws.runtime.WsServerImpl.bootServerContaine r(WsServerImpl.java:187)
    at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl .java:133)
    at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl. java:387)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.jav a:219)
    at java.lang.Thread.run(Thread.java:534)

    [6/5/07 13:19:31:911 AST] 0000000a SecurityServe E SECJ0281E: Error creating user registry object. The exception is java.lang.ClassNotFoundException: com.ibm.websphere.wmm.registry.WMMUserRegistry
    --
    ---
    ----
    Any one had similar problem or know the solution?
    Thnks in advance.



  2. Re: nodeagent...Server launched but failed initialization


    For those who may face the same problem...the solution is to copy the wmm jars to lib directory...
    In the cluster guide you will find this step after the addNode..but actually you need to copy them before federating the node otherwise you will get the same error.


  3. Smile Re: nodeagent...Server launched but failed initialization

    Solution for windows-XP and Linux
    Let WPS_HOME = C:\IBM\WebSphere

    Step (1): Go to command prompt
    Step (2): cd \wp_profile\bin
    Step (3): execute file "osgiCfgInit.bat" at command prompt

    Now, start server using startServer.bat

    Step (4): startServer.bat WebSphere_Portal -user wpsadmin -password wpsadmin

    serverName : WebSphere_Portal
    userName : wpsadmin
    password : wpsadmin

    Note: For Linux, use osgiCfgInit.sh and startServer.sh file

    Regards,
    Anadi Kumar,
    Patna, Bihar, India
    +91-9822622054

+ Reply to Thread