While using JBoss Cache 1.3.0.SP4, my application occasionally starts leaking memory. The reason for that is some unidentified rare condition that causes TreeCacheAop clone itself. Specifically, the whole application instantiates TreeCacheAop once. But sometimes (when memory starts leaking) a heap dump identifies hundreds of TreeCacheAop instances, each with its own JGroups stack, etc. I am positive that application itself does not re-create TreeCacheAop. Could it be that the cache does it itself, or maybe there are some other suggestions? Thanks a lot, Andris Birkmanis View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185373#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...