[
http://jira.jboss.com/jira/browse/JBAS-5252?page=comments#action_12414382 ]
Brian Stansberry commented on JBAS-5252:
----------------------------------------
I tore my hair out off and on over this for weeks; finally decided to move off it for a
while and do something more productive. Whenever I would analyze the heap, all references
to the leaked classloader would run through weak references that should have released.
Failures were related to use of AOP-prepared classes; tangentially discussed with the AOP
team at
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=134470.
The ReplicableClassesClassloaderLeakUnitTestCase.testNoCacheNoReplicableWar must be
something different as it doesn't involve AOP-prepared classes. I'll have a look
this week to see if there is something simple going on causing spurious failures.
Last time I looked at failures on Ejb3ClassloaderLeakUnitTestCase it was just a JNDI
lookup problem of the test EJBs.
Fix classloader leak test failures
----------------------------------
Key: JBAS-5252
URL:
http://jira.jboss.com/jira/browse/JBAS-5252
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ClassLoading
Reporter: Brian Stansberry
Assigned To: Shelly McGowan
Priority: Blocker
Fix For: JBossAS-5.0.0.CR1
Tests in org.jboss.test.classloader.leak packages are failing.
Relevant forum threads:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129122
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129201&a...
A concern is this leak is in the JDK itself, related to use of Class.forName() to provide
JDK 6 compatibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira