HA-JNDI bindings are replicated so any HA-JNDI bindings on one node would be copied to the other node. Global JNDI bindings would not be replicated as they're only bound locally. In either case, using HA-JNDI to perform a lookup should locate all local and ha bindings on nodes in the cluster.
If your HA lookup is failing from a restarted node, it seems like one of the following is the problem. 1) The lookup is being performed locally, not via ha. 2) The new node isn't recognized as part of the cluster. 3) There's a problem in the HA code and the lookup isn't being properly propagated to other nodes in the cluster. Remote lookups of locally bound objects are included in the unit tests for HA-JNDI so in general this should work properly. Sorry I don't have any more to offer on this issue as I'm not familiar with the inner workings of the server or naming service. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928790#3928790 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928790 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
