Twiddle Fails when Talking to JBoss with NameNotFoundException

Solution Unverified - Updated -

Issue

  • Twiddle fails and logs this exception to the console:
18:09:51,318 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:144)
        at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:59)
        at org.jboss.console.twiddle.command.MBeanServerCommand.queryMBeans(MBeanServerCommand.java:66)
        at org.jboss.console.twiddle.command.InvokeCommand.execute(InvokeCommand.java:283)
        at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:306)
Caused by: javax.naming.NameNotFoundException: jmx not bound
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:581)
        at org.jnp.server.NamingServer.getBinding(NamingServer.java:589)
        at org.jnp.server.NamingServer.getObject(NamingServer.java:595)
        at org.jnp.server.NamingServer.lookup(NamingServer.java:313)
...

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 4.x
    • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.