[ https://jira.jboss.org/jira/browse/JBAS-5959?page=com.atlassian.jira.plug... ] Brian Stansberry commented on JBAS-5959: ---------------------------------------- This test seems to be continually failing on the JBoss-AS-5.0.x-TestSuite-sun15 run. I tried running it today on my Windows XP laptop and it fails sometimes, passes others. Heap analysis shows the same as before. Note also this consistently passes on the JBoss-AS-5.0.x-TestSuite-jrockit16-jrockit16. Odds of a true leak that is VM specific seem low to me. Or at least of a true leak that's something we can do anything about; i.e. not a VM bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5959?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-5959: ----------------------------------- Summary: Failure on Sun VM of classloader leak tests involving AOP prepared classes (was: Intermittent failure in FieldGranularityClassloaderLeakUnitTestCase) Description: The org/jboss/test/cluster/classloader/leak/test/FieldGranularityClassloaderLeakUnitTestCase almost always (but not always) fails when the testsuite is run on the Sun VM. The org/jboss/test/classloader/leak/test/AopPreparedClassesClassloaderLeakUnitTestCase test is consistently failing when Sun 1.6 is used for the build and Sun 1.6 is used for the tests (but not when Sun 1.5 is used for the build). Both consistently pass on the JRockit tests. Heap analysis of the FieldGranularityClassloaderLeakUnitTestCase (using JBoss Profiler or hprof+jhat) after a failure always shows all paths to the leaked CL leading to WeakReferences, so the cause of the leak is unclear. was:The FieldGranularityClassloaderLeakUnitTestCase intemittently fails (once every 5-10 hudson runs). Heap analysis (using JBoss Profiler or hprof+jhat) after a failure always shows all paths to the leaked CL leading to WeakReferences, so the cause of the leak is unclear. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5959?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-5959: ----------------------------------- Fix Version/s: JBossAS-5.2.0.Beta1 (was: JBossAS-5.1.0.Beta1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5959?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-5959: ----------------------------------- Fix Version/s: Backlog (was: JBossAS-6.0.0.M3) Moving this to Backlog as I have no idea when I'll have more time to look at it; spent a ton already. If someone else wants to have a look, please re-assign. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira