Hi, We have a 2 node clustered application, with JBC 1.4.1-SP9. When we upgrade our app, we see this behaviour: 1- We stop node 1, upgrade our app, and start node 1. (Node 2 keeps processing application traffic) 2- It takes a while to start (~5 minutes) , since we have fetchInMemoryState to true. 3- The server ends starting, and initially it has around 1GB old space memory used. 4- 15 minutes later we do the same thing with node 2. We stop it, update it, and start it. It takes some time (~4 minutes), and finally loads with 1.4Gb. While this state transfer from node 1 to node 2 is happening, node 1 memory gets up to 1.9Gb. 5- After a while, there is a Full GC, and memory lowers to 1.4 Gb in node1, and 1 Gb in node 2. My questions are: 1- Why recent loaded apps have such a difference in memory? 2- Why memory fills so much during state transfer? Another thing we have seen is that we have a region with a default cache loader of 24 hours, but we have in this region data only valid for a day, until 24:00 PM, so we have a scheduler job, that removes such a node, doing a cache.remove(FQN). When we run this job, memory lowers, but after 24 hours from start it lowers much more, so we think eviction policy is happening of internal cache data for the removed nodes. Can this be possible? We have set log levels to TRACE, but we have to wait another 24 hours to see this behaviour. Thanks, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160463#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...