1 Reply Latest reply on Jun 29, 2007 10:06 AM by editha

    Jboss 5: jmx not bound

    editha

      Hi!

      I'm trying to deploy my application, which is already running on Jboss 4, in jboss 5 beta.

      When I try to lookup the RMIAdaptor with

      Properties p = new Properties(); p.put("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
      p.put("java.naming.provider.url","localhost:1099");
      
      InitialContext jndiContext = new InitialContext(p);
      
      RMIAdaptor rmiadaptor = (RMIAdaptor)jndiContext.lookup("jmx/rmi/RMIAdaptor");


      I get this error:

      javax.naming.NameNotFoundException: jmx not bound
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
      at org.jnp.server.NamingServer.getObject(NamingServer.java:556) at org.jnp.server.NamingServer.listBindings(NamingServer.java:385)
      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)


      Does any one know why this error occurs or if anything has changed in Jboss 5 that could cause this error?

      Thanks!

        • 1. Re: Jboss 5: jmx not bound
          editha

          I solved the problem. The error ocurred because

          RMIAdaptor rmiadaptor = (RMIAdaptor)jndiContext.lookup("jmx/rmi/RMIAdaptor");


          was called before the jmx-remoting.sar was deployed.