Hi, When using JbossCache in Tomcat 5.5 with JOTM as the JTA transaction manager, I stumbled upon a memory leak. After investigating with a profiler I noticed that an object I removed from JbossCache kept being referenced by a org.jboss.cache.marshall.JBCMethodCall, which was via among others a org.jboss.cache.TransactionEntry being referenced by a org.objectweb.jotm.SubCoordinator. I'm using JBossCache in the typical way: | TreeCache treeCache = new TreeCache(); | PropertyConfigurator config = new PropertyConfigurator(); | config.configure(treeCache, "META-INF/treecache.xml"); | treeCache.startService(); | | UserTransaction tx = (UserTransaction) new GenericTransactionManagerLookup().getTransactionManager(); | | tx.begin(); | | treeCache.put( "/test" , "foo", someTestObject ); | | tx.commit(); | | treeCache.removeData( "/test" ); // extra, for test | treeCache.remove( "/test" ); | | treeCache.stopService(); | treeCache.destroyService(); | After executing this code, "someTestObject" remains in memory. Is this a known problem? Could it be a bug in JOTM or is the problem with JBossCache? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028001#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...