[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1442) Ejb3ClassloaderLeakUnitTestCase failures in AS testsuite

[Adrian Brock (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12429076#action_12429076 ] 

Adrian Brock commented on EJBTHREE-1442:
----------------------------------------

There are nothing but weak references to the classloader.
See ClassLoader.html

However, what there is a proxy for one the ejb interfaces registered against the wrong classloader
See Proxy.html - which basically repeats lots of times showing $Proxy156 in BaseClassLoader0x97252960
which is not the same as the classloader for that interface shown in ClassLoader.html, i.e.
BaseClassLoader0x988eb568.

Steps to reproduce this analysis.

1) Run the test using Sun's JDK6
2) Use jps to locate the pid for JBoss
3) jmap -dump:live,file=dump <pid>
4) jhat dump
5) http://localhost:7000
6) Find BaseClassLoader click on it to show the class
7) Click on Instances/Exclude subclasses
8) Go through the instances and look at the classes/elementData until to see the leak test classes
and therefore identified the classloader instance
9) Run "Other Queries/Exclude WeakReferences" to see what roots reference the classloader
and the class(es) respectively.

> Ejb3ClassloaderLeakUnitTestCase failures in AS testsuite
> --------------------------------------------------------
>
>                 Key: EJBTHREE-1442
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1442
>             Project: EJB 3.0
>          Issue Type: Bug
>            Reporter: Brian Stansberry
>            Assignee: Andrew Lee Rubinger
>            Priority: Critical
>             Fix For: 1.0.0-Beta2
>
>         Attachments: ClassLoader.html, Proxy.html
>
>
> The Ejb3ClassloaderLeakUnitTestCase tests started failing on Jul 17 (see https://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/746/).  I ran the test with the JBoss Profiler analysis of the classloader leak enabled and found that a proxy remains bound in JNDI after bean undeploy, leaking the CL.  I will attach the classloader leak report.

-- 
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