[
http://jira.jboss.com/jira/browse/JBAS-5252?page=comments#action_12414381 ]
Dimitris Andreadis commented on JBAS-5252:
------------------------------------------
Has someone looked more into this? AFAICT, the leaks are coming and going from run to
run.
E.g. from a relatively recent one:
org.jboss.test.classloader.leak.test.Ejb3ClassloaderLeakUnitTestCase.testSimpleEjb
org.jboss.test.cluster.classloader.leak.test.FieldGranularityClassloaderLeakUnitTestCase(ClusteredClassLoaderLeak).testSimpleReplicableWar
org.jboss.test.cluster.classloader.leak.test.ReplicableClassesClassloaderLeakUnitTestCase(ClusteredClassLoaderLeak).testNoCacheNoReplicableWar
org.jboss.test.cluster.classloader.leak.test.ReplicableClassesClassloaderLeakUnitTestCase(ClusteredClassLoaderLeak).testNoCacheReplicableWar
org.jboss.test.cluster.classloader.leak.test.ReplicableClassesClassloaderLeakUnitTestCase(ClusteredClassLoaderLeak).unknown
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