[jboss-dev-forums] [Design of Clustering on JBoss (Clusters/JBoss)] - JBAS-4574 and JBAS-1476

[adrian@jboss.org]

As mentioned on JBAS-4574 you need to discuss things on the forums
before opening JIRA issues. This avoids wrong conclusions and hacks
to workaround problems (JBAS-1476) when the original problem should be fixed.

On JBAS-4574 Ben appears to claim (its not clear actually what he claims)
that the problem is that naming context is getting cached.
This is irrelevant. For HAJNDI the naming context uses the cluster view
for the transport (regardless of how many naming contexts you create).

It is the fact that it is using the cluster view from a different cluster instance (JBAS-1476)
that is the problem. It doesn't update the view because the "view change" is less
than it previously was.

That's not to say that there isn't a case for flushing the cached naming context
on a naming CommunicationException and transparently recreating it,
but that doesn't help in thise case since the underlying problem will not be fixed.
And such a change would require significant testing.

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

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