Are you using 2.0.0 GA? We have encountered this problem for 2.0.0 GA and never solved it properly. Currently we have a smelly workaround for it. I have a simple test project for replicating this (for v2.0.0), but its real easy to replicate: Setup one node that is making changes to a couple of nodes to the cache and bring up a new node that joins the cluster. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119819#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...