"[EMAIL PROTECTED]" wrote : Have you tried using both?
I quess we cold try if that helps...
Below is a bit more detailed example of the hanging up of our cluster. It isn't
excatly the same I described above (new coordinator is assigned when current
dies), but still deals with the problem relate
"[EMAIL PROTECTED]" wrote : Have you looked at
http://wiki.jboss.org/wiki/FDVersusFD_SOCK ?
We've also tried FD_SOCK, but it seems that it won't solve the problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163757#4163757
Reply to the post :
http://www.
"[EMAIL PROTECTED]" wrote : The next available member takes over as a
coordinator.
Ok, that makes sense.
Still, I'm confused with the behaviour of our cluster. We'we been trying
different configurations for the FD and still are occasionally experiencing
problems with the lost coordinator.
Vi
Hello,
JBossCache and JGroups Services documentation
(http://docs.jboss.org/jbossas/jboss4guide/r4/html/jbosscache.chapt.html#jbosscache-jgroups-fd-fd)
states that when FD discovery protocol is being used, the current group
coordinator is responsible of updating the cluster's view when a node o
