Another not-too-elegant approach would be to start a transaction and read the node, then mark the node as in use. This way, 1) local evictions won't remove your node because you have marked it as in use. 2) remote evictions won't remove your node since your tx has a lock on it. Remote evictions will in fact fail and be put on a recycle queue if you are using synchronous replication, or fail quietly if you are using async replication. When you are done with your update, call unmarkNodeCurrentlyInUse() and commit your transaction to release locks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144095#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...