LOL. You're lucky. You tend to ask questions when I've got a few spare minutes to answer. :-) To get that to work you'd have to do some tricks with the configuration of buddy replication. What you want is: 1) Node 1 always chooses node2 as buddy. 2) Node 2 chooses either 1 or 3. 3) Node 3 always chooses node2 as buddy. #2 is simple; just include all 3 nodes in the same buddy pool. For #1 and #3 you would probably need to create your own implementation of the BuddyLocator interface, one that accepts a config option identifying node2 as the preferred buddy. As to whether it's worthwhile, it depends on how much load your app's usage of session replication puts on a buddy -- how much memory and cpu is used handling providing backup for a buddy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023774#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...