Adrian, I assume you are referring to the "forceReleaseOnSoftReferences()" method in JVMTIInterface? Yes, that does deliberately fill memory until OOME if necessary, and then forces a GC to try to recover. The "[JVMTIInterface] 4069000 references received" logging Andrew reported occurs later in the process when JVMTIInterface is trying to analyze the heap snapshot it took after having returned from forceReleaseOnSoftReferences(). All of the heap analysis data is being kept in the heap as well; I've found that that standard heap size isn't adequate to do the full analysis w/ AS 5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175163#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...