[jboss-user] [Clustering/JBoss] - Re: ServiceLocator and caching home interfaces in a cluster.

[JerryGauth]

I can advise about HA-JNDI.  If you use the provider url of localhost:1100, your context will be associated with HA-JNDI.  If you then lookup objects via that context, the lookup will utilize HA-JNDI.  If you bind something using that context, the binding will be stored in HA-JNDI and replicated throughout the cluster.

Note that all JNDI bindings can be listed using the JNDIView service.  From the JMX Console, select service=JNDIView and then invoke either the list( ) or listXML( ) methods.  The output will display all of your JNDI bindings.  The last section of the output shows HA-JNDI bindings; anything listed here is stored in HA-JNDI and replicated on all nodes.

HA-JNDI will successfully lookup any JNDI binding, regardless of which node has the binding.  Standard JNDI will only successfully lookup any JNDI (not HA-JNDI) binding on the node associated with the lookup request.

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

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