We haven't got such information published in a wiki or documentation but I believe you should be able to figure out what the state is composed of by looking at the code in the different org.jboss.cache.remoting.jgroups.ChannelMessageListener.setState calls that effectively delegate the state handling to org.jboss.cache.statetransfer.DefaultStateTransferManager.setState(). Check this code in the JBossCache version that you're using or preferably, since JBoss Cache is now in maintenance mode, I'd suggest you use Infinispan instead. Note that Infinispan, even though it's a new project, it's based on some code from JBoss Cache, so it's pretty robust already for all features JBoss Cache provided (non blocking state transfer, async/sync replication, mvcc locking...etc). Besides, we have switched from a tree structure to a map and I believe it'll be easier to deal with such structure from a client's perspective. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240288#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...