Will look into adding your tests, but for now: 1) This should pass - and it does on Branch_JBossCache_1_4_0 (off which 1.4.1.SP1 was recently released)
2) Changing the order with which you restart caches is a problem. There is no way of knowing which cache's persistent state is "correct". Therefore, the first one that comes back up is treated as correct. When the 2nd cache comes up, it looks for any existing members in the cluster and requests state from that member. If that member happens to have older state (since it was shut down and missed stuff) then that node is still treated as holding the true data rep since there is no way of knowing that it was shut down for a while, things moved on, and then the rest of the cluster was shut down. One way around this is to use a shared cache loader so that all cache instances use the same persistent store. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013601#4013601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013601 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
