This was tested on both 3.2.8 sp1 and 4.0.4 GA. Within a subnet I confiured two nodes A and B using the TCP protocol for JGroup(I'm primarily interested in WAN cluster for site failover so next step would have been to separate the nodes across WAN).
Node A is started and runs in Master mode. Node B is started and joins the DefaultPartition cluster along with node A in Slave mode. So far so good. Now I disconnect the lan line on the Node B machine. It fails to ping Node A and thus changes its mode to Master. Now plug the connection back in. Node B never joins the DefaultPartition cluster with node A. Node B continues to run in Master mode. I'd expect it to join the old cluster back and reset its mode to Slave from Master. This will present a serious issue of trying to use Singleton Tasks in a cluster. Any suggestions from anyone if the behavior I'm oberving is not because of some n/w configuration issue at Jgroup level for recovery? Thanks Kumar Pandey View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950040#3950040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950040 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
