So after profiling this the problem looks to be recent changes in org.jboss.util.timeout.TimeoutFactory as the leaks are related to transaction timeouts. By clearing the TimeoutFactory$TimeoutImpl references the test gets past the OME, but there are 73k TimeoutFactory$TimeoutImpl left after the test has completed and has been undeployed. One gc root is the java.util.TimerThread task queue.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Saturday, January 21, 2006 2:17 PM > To: Bill Burke > Cc: [email protected] > Subject: [JBoss-dev] RE: ejb3-4.0-testsuite Build Failed > > This is just the org.jboss.ejb3.test.microbench.unit.BenchUnitTestCase > requiring too much memory. Memory usage during this test goes > from 40m to 130m even using the default config so the memory > usage of this needs to be looked at. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
