Why are remote JNDI lookups sometimes occurring on the wrong JBoss EAP 4/5 instance

Solution Verified - Updated -


  • When dealing with one node directly (svc1), things work great.  When I added a second node to the cluster (svc2) twiddle running against svc1 would occasionally invoke an MBean operation on svc2.
  • Twiddle is not always connecting to the host specified by the -s argument.  Instead, it is sometimes connecting to the correct host but other times it connects to one of the other nodes in the JBoss Enterprise Application Platform (EAP) cluster.
    The following should connect to svc1:
./twiddle.sh -s svc1:1099 -u admin -p admin get jboss.j2ee:ear=example-ear-project1.ear,jar=EARProject1EJB.jar,name=ejb/Calculator,service=EJB3

Instead, on occasions, svc2 is used instead of svc1.

  • Remote JNDI lookups will sometimes be performed against other JBoss Enterprise Application Platform (EAP) instances on our network.
  • Twiddle collects information from a JBoss server even though it is not running


  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 4.3
    • 5.x
  • org.jnp.interfaces.NamingContext provided by JBoss EAP

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