As Scott noted, HAJNDI 's list() and listBindings() operations are based upon the corresponding JNDI operations. Consequently they only return entries relative to the HAJNDI tree. It is possible to bind to the HAJNDI tree although this probably isn't done by any JBoss modules right now. Entries bound to the HAJNDI tree are replicated throughout the cluster and consequently readily available on all nodes via HAJNDI. There's probably no reason why HAJNDI can't offer new operations that return all bindings in a cluster. As Brian noted, it would be necessary to determine how to handle situations where objects are bound under the same key on multiple local nodes. Alternatively, the operation might return all bindings for all nodes in the cluster, identifying the node associated with each key/value binding. For reference - HAJNDI in JBoss 5 is based on JBossCache but JBossCache is only used for entries bound in HAJNDI. Local bindings are outside the scope of HAJNDI and currently aren't stored in JBossCache. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021255#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...