From my point of view the HAJNDI tree does not make much sense except
for components that are only available on a subset of nodes within the cluster. In my case
that would be HA-JMS because it can only run as a HA-Singleton.
This means that the HAJNDI tree cannot use the shortcut of just using the local JNDI tree
because it may or may not be the Master node.
What I do not understand is the fact that by default nothing is bound to the HAJNDI. This
means that when I need to lookup a HA-JMS object inside the cluster I will lookup the
object every time (at least that is the case for 4.0.4 and 4.05) even though that is an
expensive remote lookup over the entire cluster (in the worst case) and that on every
lookup because the found object is not cached inside the TreeHead, isn't it.
-Andy
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020992#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...