1 Reply Latest reply on Dec 27, 2006 5:19 AM by Mahendra Kutare

    Twiddle executions throws NameNotFoundException: jmx not bou

    Mahendra Kutare Newbie

      While trying to run twiddle on my Jboss 4.0.4 installation it throws the following error -

      sh ./twiddle.sh -s 10.129.50.4 serverinfo --count

      04:29:29,352 ERROR [Twiddle] Exec failed
      org.jboss.util.NestedRuntimeException: jmx not bound; - nested throwable: (javax.naming.NameNotFoundException: jmx not bound) at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:143)
      at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:59)
      at org.jboss.console.twiddle.command.ServerInfoCommand.execute(ServerInfoCommand.java:130)
      at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305)
      Caused by: javax.naming.NameNotFoundException: jmx not bound
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
      at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
      at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
      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:585)
      at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
      at sun.rmi.transport.Transport$1.run(Transport.java:153)
      at java.security.AccessController.doPrivileged(Native Method)
      at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
      at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
      at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
      at java.lang.Thread.run(Thread.java:595)
      at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
      at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
      at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
      at javax.naming.InitialContext.lookup(InitialContext.java:351)
      at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:250)
      at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:268)
      at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:62)
      at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:139)
      ... 3 more

      Can anyone please explain this and possible solution ?

      - Mahendra

        • 1. Re: Twiddle executions throws NameNotFoundException: jmx not
          Mahendra Kutare Newbie

          For benefit of those, who may be facing this -

          a) Twiddle uses default JNDI name of - jmx/invoker/RMIAdaptor

          b) If you application deployment does not have jmx-invoker-service.xml , JMX will not be registered with JNDI

          c) Copy jmx-invoker-service.xml from all/deploy to [my-app]/deploy

          d) Start Jboss

          e) Run twiddle script as - sh ./twiddle.sh -s 10.129.50.4:1100 -a jmx/invoker/RMIAdaptor invoke jboss:service=JNDIView list true
          to test if twiddle is running fine.

          f) It displays the entire JNDIView

          - Mahendra