Yes, the HA-JNDI client includes an optimization to route the call locally if the client is in the same VM as the server. OK, now I understand your use case better. Here's a workaround: Use HA-JNDI to get an MBeanServerConnection. Invoke on it to get the "CurrentView" attribute of the "jboss:service=DefaultPartition" mbean. That will return you a Vector. Iterate through the vector and call getName() on each element; that returns a string with the JNDI address and port of that member of the cluster. You can then do a regular JNDI lookup using that string as your PROVIDER_URL. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152458#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...