Moving to Jboss-Cache 1.4.1 SP4 and Jgroups 2.4.1SP3 seems to resolve this issue.
There is an interesting memory usage pattern occuring though: After the server starts up
we see a gradual increase in memory usage on one node in the cluster. It approaches the
Maximum allocated to the instance, then drops off and behaves.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069832#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...