[jboss-dev-forums] [Design of JBoss Internal Benchmarking] - Changes required in jboss-specj2004-kit-1.3.7 for using TWID

[mahendra_kutare]

Hi,

I am using jboss-specj2004-kit-1.3.7 with jboss4.0.4 and MySQL 5.0.18.

My application is deployed and running fine am also able to see the JMX web console.

But when i  am trying to run the TWIDDLE script ./twddle.sh it throws following NAMENOTFOUNDEXCEPTION  -

[mahendra at autonomic bin]$ 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

Are there any specific changes required in specj2004 server instance deployed through the kit to resolve this and get TWIDDLE scripts running ??

- Mahendra

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995994#3995994

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995994