Topic
4 replies Latest Post - ‏2011-06-10T12:08:56Z by UshaRaj
SystemAdmin
SystemAdmin
37426 Posts
ACCEPTED ANSWER

Pinned topic HELP----Server launched but failed initialization?!!!!

‏2007-02-04T05:41:26Z |
Hi all,
I am new to websphere. I install the websphere 6.0 network deployment core product and then the default application server profile Appsrv01.
I can start the server1 successfully : install_root/bin/startServer.sh server1

But when I install a deployment Manager profile later and add the Appsrv01 node to the deployment manager cell by "install_root/profiles/appsrv01/bin/addNode.sh", I can not start the server1 any more. Following are the error When I use "install_root/bin/startServer.sh server1":
ADMU0116I: Tool information is being logged in file
/opt/IBMWebsphere/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. Server log files should
contain failure information.

And also the information in the SystemErr.log:

2/3/07 1:55:48:003 EST 0000000a SystemErr R com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:182)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:120)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:378)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
Caused by: com.ibm.ws.exception.RuntimeError: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:821)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:356)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:173)
... 9 more
Caused by: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
at com.ibm.ejs.oa.LocationService.register(LocationService.java:205)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:140)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:339)
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:340)
... 13 more
Caused by: org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:3948)
at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:627)
at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3332)
at com.ibm.ejs.oa.LocationService.register(LocationService.java:162)
... 16 more
Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:443)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:437)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:162)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:81)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:175)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:306)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:377)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3457)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3374)
at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:157)
... 20 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:331)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:196)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.connect(Socket.java:428)
at java.net.Socket.<init>(Socket.java:335)
at java.net.Socket.<init>(Socket.java:150)
at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:308)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:374)
... 29 more

2/3/07 1:55:48:027 EST 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:182)
2/3/07 1:55:48:028 EST 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:120)
2/3/07 1:55:48:028 EST 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:378)
2/3/07 1:55:48:028 EST 0000000a SystemErr R at com.ibm.ws.runtime.WsServer.main(WsServer.java:50)
2/3/07 1:55:48:031 EST 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2/3/07 1:55:48:031 EST 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
2/3/07 1:55:48:031 EST 0000000a SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
2/3/07 1:55:48:031 EST 0000000a SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
2/3/07 1:55:48:031 EST 0000000a SystemErr R at java.lang.reflect.Method.invoke(Method.java:391)
2/3/07 1:55:48:032 EST 0000000a SystemErr R at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
2/3/07 1:55:48:032 EST 0000000a SystemErr R Caused by: com.ibm.ws.exception.RuntimeError: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
2/3/07 1:55:48:035 EST 0000000a SystemErr R at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:343)
2/3/07 1:55:48:035 EST 0000000a SystemErr R at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:821)
2/3/07 1:55:48:035 EST 0000000a SystemErr R at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
2/3/07 1:55:48:035 EST 0000000a SystemErr R at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:356)
2/3/07 1:55:48:036 EST 0000000a SystemErr R at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:173)
2/3/07 1:55:48:036 EST 0000000a SystemErr R ... 9 more
2/3/07 1:55:48:036 EST 0000000a SystemErr R Caused by: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
2/3/07 1:55:48:039 EST 0000000a SystemErr R at com.ibm.ejs.oa.LocationService.register(LocationService.java:205)
2/3/07 1:55:48:039 EST 0000000a SystemErr R at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:140)
2/3/07 1:55:48:039 EST 0000000a SystemErr R at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:339)
2/3/07 1:55:48:039 EST 0000000a SystemErr R at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:340)
2/3/07 1:55:48:079 EST 0000000a SystemErr R ... 13 more
2/3/07 1:55:48:079 EST 0000000a SystemErr R Caused by: org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
2/3/07 1:55:48:079 EST 0000000a SystemErr R at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:218)
2/3/07 1:55:48:080 EST 0000000a SystemErr R at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:3948)
2/3/07 1:55:48:080 EST 0000000a SystemErr R at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:627)
2/3/07 1:55:48:082 EST 0000000a SystemErr R at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:3332)
2/3/07 1:55:48:087 EST 0000000a SystemErr R at com.ibm.ejs.oa.LocationService.register(LocationService.java:162)
2/3/07 1:55:48:095 EST 0000000a SystemErr R ... 16 more
2/3/07 1:55:48:095 EST 0000000a SystemErr R Caused by: org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=localhost.localdomain,port=9900 vmcid: IBM minor code: E02 completed: No
2/3/07 1:55:48:095 EST 0000000a SystemErr R at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:443)
2/3/07 1:55:48:095 EST 0000000a SystemErr R at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:437)
2/3/07 1:55:48:096 EST 0000000a SystemErr R at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:162)
2/3/07 1:55:48:096 EST 0000000a SystemErr R at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:81)
2/3/07 1:55:48:096 EST 0000000a SystemErr R at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:175)
2/3/07 1:55:48:099 EST 0000000a SystemErr R at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:306)
2/3/07 1:55:48:099 EST 0000000a SystemErr R at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:377)
2/3/07 1:55:48:099 EST 0000000a SystemErr R at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3457)
2/3/07 1:55:48:099 EST 0000000a SystemErr R at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3374)
2/3/07 1:55:48:099 EST 0000000a SystemErr R at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:157)
2/3/07 1:55:48:100 EST 0000000a SystemErr R ... 20 more
2/3/07 1:55:48:100 EST 0000000a SystemErr R Caused by: java.net.ConnectException: Connection refused
2/3/07 1:55:48:102 EST 0000000a SystemErr R at java.net.PlainSocketImpl.socketConnect(Native Method)
2/3/07 1:55:48:103 EST 0000000a SystemErr R at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:331)
2/3/07 1:55:48:103 EST 0000000a SystemErr R at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:196)
2/3/07 1:55:48:103 EST 0000000a SystemErr R at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:183)
2/3/07 1:55:48:103 EST 0000000a SystemErr R at java.net.Socket.connect(Socket.java:478)
2/3/07 1:55:48:104 EST 0000000a SystemErr R at java.net.Socket.connect(Socket.java:428)
2/3/07 1:55:48:104 EST 0000000a SystemErr R at java.net.Socket.<init>(Socket.java:335)
2/3/07 1:55:48:106 EST 0000000a SystemErr R at java.net.Socket.<init>(Socket.java:150)
2/3/07 1:55:48:108 EST 0000000a SystemErr R at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:308)
2/3/07 1:55:48:112 EST 0000000a SystemErr R at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:374)
2/3/07 1:55:48:132 EST 0000000a SystemErr R ... 29 more
What is the problem?
Thanks a lot to any comments!!

Best,
-Qian
Updated on 2011-06-10T12:08:56Z at 2011-06-10T12:08:56Z by UshaRaj
  • SystemAdmin
    SystemAdmin
    37426 Posts
    ACCEPTED ANSWER

    Re: HELP----Server launched but failed initialization?!!!!

    ‏2007-02-04T11:58:03Z  in response to SystemAdmin
    qianhangwei@gmail.com wrote:
    > Hi all,
    > I am new to websphere. I install the websphere 6.0 network deployment core product and then the default application server profile Appsrv01.
    > I can start the server1 successfully : install_root/bin/startServer.sh server1
    >
    > But when I install a deployment Manager profile later and add the Appsrv01 node to the deployment manager cell by "install_root/profiles/appsrv01/bin/addNode.sh", I can not start the server1 any more. Following are the error When I use "install_root/bin/startServer.sh server1":
    > ADMU0116I: Tool information is being logged in file
    > /opt/IBMWebsphere/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
    > ADMU0128I: Starting tool with the AppSrv01 profile
    > ADMU3100I: Reading configuration for server: server1
    > ADMU3200I: Server launched. Waiting for initialization status.
    > ADMU3011E: Server launched but failed initialization. Server log files should
    > contain failure information.
    >
    > And also the information in the SystemErr.log:
    >
    > 2/3/07 1:55:48:003 EST 0000000a SystemErr R com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:

    snip

    >
    > What is the problem?
    > Thanks a lot to any comments!!
    >
    > Best,
    > -Qian
    >

    The line from your stacktrace I left in seems to say it all.

    Typically, with ND you will not stop and start servers with
    startServer.sh. You'll start and stop servers through the DM, which
    talks to the Node Agents, which manage the appservers.

    Ken
    • SystemAdmin
      SystemAdmin
      37426 Posts
      ACCEPTED ANSWER

      Re: HELP----Server launched but failed initialization?!!!!

      ‏2007-02-04T13:21:37Z  in response to SystemAdmin
      Ken Hygh wrote:

      > Typically, with ND you will not stop and start servers with
      > startServer.sh.

      Or even if you do, start the dMgr first, then the node agent, then the
      server.
      • SystemAdmin
        SystemAdmin
        37426 Posts
        ACCEPTED ANSWER

        Re: HELP----Server launched but failed initialization?!!!!

        ‏2007-02-09T06:52:44Z  in response to SystemAdmin
        Hi,Thanks a lot for you two guys' reply!

        Now I start the Deployment manager first using: profile_root/Dmgr01/bin/startManager.sh

        And then start the node agent using:
        profile_root/AppSrv01/startNode.sh

        Both the above two steps go successfully.
        Then I tried to start the server1. I tried following ways:
        1.profile_root/AppSrv01/startServer.sh server1
        But still this returns error and I found nothing in the server1's SystemErr.log and SystemOur.log fils.
        2. Use browser: Servers->application servers, select server1 and click start.
        This did not work either,complaining "localhostNode01/server1 server could not be started View JVM logs for further details."

        Where can I find the JVM logs? Are the above two ways I tried correct?
        Sorry for the stupid questions. I am very new to websphere.

        Thanks a lot.

        Best wishes,
        -Qian
        • UshaRaj
          UshaRaj
          1 Post
          ACCEPTED ANSWER

          Re: HELP----Server launched but failed initialization?!!!!

          ‏2011-06-10T12:08:56Z  in response to SystemAdmin
          the steps tried are correct.
          JVM logs path can be found in below path from IBM Console --
          Application servers > server1 > Process definition > Logging and Tracing > JVM Logs

          The environment variables can be modified in IBM Console -- Environment -- WebSphere variables