That issue if for redeployment leakages. But if we add some comment it could become general memory leaks IMO.
Anyway, at this point I'm creating a testcase for JMS, using JVMTIInterface from JBossProfiler. Basically I'm doing: // I have to pre-create every service. | | // Execute the testcase at least once (to force creation of everything is supposed to be created) | | Map inventory1 = jvmti.produceInventory(); | | ..... execute the testcase again. | | | // clear some stuff | | Map inventory2 = jvmti.produceInventory(); | | assertTrue(jvmti.compareInventories(System.out,inventory1,inventory2,....); | | If nothing was created, compareInventories is going to pass, what would mean no memory leaks. This way we will avoid regressions of memory leaks on the future. I guess we could use the same idea with this testcase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3948757#3948757 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3948757 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
