4 Replies Latest reply on Nov 11, 2005 12:03 PM by 807581

    Trouble starting Application Server Enterprise Edition 8.1 Cluster

    807581
      I am getting the follwoing error when trying to start a cluster. Does anyone know the problem

      Operation 'start' failed in 'cluster' Config Mbean. Target exception message: All server instances in cluster umslogonnew were not started. Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector
        • 1. Re: Trouble starting Application Server Enterprise Edition 8.1 Cluster
          807581
          Is the node agent running? This error shows up when the Domain Admin Server is not able to connect to the node-agent that is associated with server instances.
          • 2. Re: Trouble starting Application Server Enterprise Edition 8.1 Cluster
            807581
            How do I check if the node agent is running. If it is not how do I start it up.

            Many thanks

            Dave
            • 3. Re: Trouble starting Application Server Enterprise Edition 8.1 Cluster
              807581
              Dave,
              Can you do <P>

              list-node-agents --user admin-user --password   admin-password --port admin-port --host admin-server-host 

              <P>

              It should show you the status of the node-agents that you created.
              </P>

              Thanks,
              Kedar
              • 4. Re: Trouble starting Application Server Enterprise Edition 8.1 Cluster
                807581
                Yes the node agents are up and running. I have no problem viewing other clusters havings instances on the same machines. My problem comes when I try to delete instances under a cluster. I was having these problems so I created a simple cluster with 2 instances to test them. I tried starting the instances and then stopping them about 2 times. I then tried to delete 1 of the 2 instances and got the error. This is the error on the JAS server
                Enter Admin User:
                Enter Admin Password:
                Enter Master Password:
                Enter Other Password Information (or ctrl-D or ctrl-Z):
                [#|2005-11-10T16:33:32.012+0000|INFO|sun-appserver-ee8.1_02|javax.ee.enterprise.system.nodeagent|_ThreadID=45;|NAGT0039:Synchonization for ums1-itc - SUCCEEDED! and took 67153 milliseconds|#]
                
                [#|2005-11-10T16:40:54.718+0000|INFO|sun-appserver-ee8.1_02|javax.ee.enterprise.system.nodeagent|_ThreadID=46;|NAGT0019:The nodeagent is stopping the server instance ums1-itc|#]
                
                [#|2005-11-10T16:44:15.438+0000|INFO|sun-appserver-ee8.1_02|javax.ee.enterprise.system.nodeagent|_ThreadID=47;|NAGT0018:The nodeagent is starting the server instance ums1-itc|#]
                
                Enter Admin User:
                Enter Admin Password:
                Enter Master Password:
                Enter Other Password Information (or ctrl-D or ctrl-Z):
                [#|2005-11-10T16:45:09.918+0000|INFO|sun-appserver-ee8.1_02|javax.ee.enterprise.system.nodeagent|_ThreadID=47;|NAGT0039:Synchonization for ums1-itc - SUCCEEDED! and took 54359 milliseconds|#]
                
                [#|2005-11-10T16:50:26.398+0000|WARNING|sun-appserver-ee8.1_02|javax.management.remote.misc|_ThreadID=48;|Failed to check the connection: java.net.SocketTimeoutException: Read timed out|#]
                
                [#|2005-11-10T16:50:26.468+0000|WARNING|sun-appserver-ee8.1_02|javax.management.remote.misc|_ThreadID=49;|Failed to check the connection: java.net.SocketTimeoutException: Read timed out|#]
                
                [#|2005-11-10T16:50:26.488+0000|WARNING|sun-appserver-ee8.1_02|javax.management.remote.misc|_ThreadID=50;|Failed to check the connection: java.net.SocketTimeoutException: Read timed out|#]
                
                [#|2005-11-10T16:50:26.508+0000|WARNING|sun-appserver-ee8.1_02|javax.management.remote.misc|_ThreadID=51;|Failed to check the connection: java.net.SocketTimeoutException: Read timed out|#]
                
                [#|2005-11-10T16:50:26.638+0000|WARNING|sun-appserver-ee8.1_02|javax.management.remote.misc|_ThreadID=52;|Failed to check the connection: java.net.SocketTimeoutException: Read timed out|#]
                
                [#|2005-11-10T16:50:26.688+0000|WARNING|sun-appserver-ee8.1_02|javax.management.remote.misc|_ThreadID=53;|Failed to check the connection: java.net.SocketTimeoutException: Read timed out|#]
                
                [#|2005-11-10T16:55:14.854+0000|INFO|sun-appserver-ee8.1_02|javax.ee.enterprise.system.nodeagent|_ThreadID=54;|NAGT0019:The nodeagent is stopping the server instance ums1-itc|#]
                
                [#|2005-11-10T17:05:15.518+0000|INFO|sun-appserver-ee8.1_02|javax.ee.enterprise.system.nodeagent|_ThreadID=54;|server ums1-itc has admin channel status of not running and desired status of running|#]
                
                [#|2005-11-10T17:05:15.519+0000|WARNING|sun-appserver-ee8.1_02|javax.ee.enterprise.system.nodeagent|_ThreadID=54;|NAGT0009:Node Agent could not STOP instance ums1-itc.
                com.sun.enterprise.ee.nodeagent.ProcessManagerException: com.sun.enterprise.admin.servermgmt.InstanceException: Subprocess timed out after 600000mS
                        at com.sun.enterprise.ee.nodeagent.ProcessInstanceInternal.stopInstance(ProcessInstanceInternal.java:74)
                        at com.sun.enterprise.ee.nodeagent.ProcessManager.stopProcess(ProcessManager.java:117)
                        at com.sun.enterprise.ee.nodeagent.NodeAgent.stopInstance(NodeAgent.java:291)
                        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                        at java.lang.reflect.Method.invoke(Method.java:324)
                        at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
                        at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
                        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
                        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
                        at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1409)
                        at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:82)
                        at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1246)
                        at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1342)
                        at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:783)
                        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                        at java.lang.reflect.Method.invoke(Method.java:324)
                        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
                        at sun.rmi.transport.Transport$1.run(Transport.java:148)
                        at java.security.AccessController.doPrivileged(Native Method)
                        at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
                        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
                        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
                        at java.lang.Thread.run(Thread.java:534)
                Caused by: com.sun.enterprise.admin.servermgmt.InstanceException: Subprocess timed out after 600000mS
                        at com.sun.enterprise.ee.admin.servermgmt.EEInstancesManager.stopInstance(EEInstancesManager.java:190)
                        at com.sun.enterprise.ee.nodeagent.ProcessInstanceInternal.stopInstance(ProcessInstanceInternal.java:71)
                        ... 26 more
                Caused by: com.sun.enterprise.admin.servermgmt.InstanceException: Subprocess timed out after 600000mS
                        at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.execute(PEInstancesManager.java:484)
                        at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.stopInstance(PEInstancesManager.java:265)
                        at com.sun.enterprise.ee.admin.servermgmt.EEInstancesManager.stopInstance(EEInstancesManager.java:188)
                        ... 27 more
                Caused by: com.sun.enterprise.util.ExecException: Subprocess timed out after 600000mS
                        at com.sun.enterprise.util.ProcessExecutor.execute(ProcessExecutor.java:276)
                        at com.sun.enterprise.util.ProcessExecutor.execute(ProcessExecutor.java:195)
                        at com.sun.enterprise.util.ProcessExecutor.execute(ProcessExecutor.java:178)
                        at com.sun.enterprise.admin.servermgmt.pe.PEInstancesManager.execute(PEInstancesManager.java:480)
                        ... 29 more
                |#]
                This is the error I get on the DAS server.
                [#|2005-11-11T11:08:52.212+0000|WARNING|sun-appserver-ee8.1_02|javax.ee.enterprise.system.tools.admin|_ThreadID=9389;|EEADM0005:An exception occurred listing server instances with target ums2-itc.
                com.sun.enterprise.admin.servermgmt.InstanceException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector
                        at com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.getRuntimeStatus(ServersConfigBean.java:157)
                        at com.sun.enterprise.ee.admin.configbeans.ServersConfigBean$GetRuntimeStatusTask.run(ServersConfigBean.java:104)
                        at java.lang.Thread.run(Thread.java:534)
                Caused by: com.sun.enterprise.admin.servermgmt.InstanceException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector
                        at com.sun.enterprise.ee.admin.clientreg.InstanceRegistry.getInstanceConnection(InstanceRegistry.java:132)
                        at com.sun.enterprise.ee.admin.proxy.InstanceProxy.getConnection(InstanceProxy.java:83)
                        at com.sun.enterprise.ee.admin.proxy.InstanceProxy.invoke(InstanceProxy.java:155)
                        at $Proxy18.getRuntimeStatus(Unknown Source)
                        at com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.getRuntimeStatus(ServersConfigBean.java:149)
                        ... 2 more
                Caused by: com.sun.enterprise.ee.admin.servermgmt.AgentException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector
                        at com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConnectorRegistry.java:289)
                        at com.sun.enterprise.ee.admin.clientreg.InstanceRegistry.getInstanceConnection(InstanceRegistry.java:130)
                        ... 6 more
                Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: management/rmi-jmx-connector
                        at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:317)
                        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
                        at com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connectToServer(JMXConnectorRegistry.java:338)
                        at com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:317)
                        at com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:178)
                        at com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConnectorRegistry.java:258)
                        ... 7 more
                Caused by: javax.naming.NameNotFoundException: management/rmi-jmx-connector
                        at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:90)
                        at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:185)
                        at javax.naming.InitialContext.lookup(InitialContext.java:347)
                        at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1807)
                        at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1777)
                        at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:259)
                        ... 12 more
                Regards

                David