[jboss-jira] [JBoss JIRA] Updated: (JBAS-4359) Fix the org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase

Mon Apr 23 22:57:30 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBAS-4359?page=all ]

Clebert Suconic updated JBAS-4359:
----------------------------------

    Assignee: Ron Sigal  (was: Clebert Suconic)

Ron... I'm assigning this to you..

You have the fix attached to this issue. All you need to do is to patch jboss-remoting 2.2 (maybe create a SP2?) with the fix.

I tried to commit this myself on remoting branch, but I was confused about what branch to use, since I didn't recognize what branch to use based in your naming standard.

> Fix the org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase
> ------------------------------------------------------------------------
>
>                 Key: JBAS-4359
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4359
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>            Reporter: Dimitris Andreadis
>         Assigned To: Ron Sigal
>            Priority: Blocker
>             Fix For: JBossAS-4.2.0.GA
>
>         Attachments: apr212007.zip, JavaSerializationManager.java, ObjectInputStreamWithClassLoader.java
>
>
> Brian, did the initial analysis for the failure:
> "The classloader leak test timing out is basically due to a failure; different tests in the class are all encountering the same leak and taking time trying to force a release, so it times out.
> The failure is on a remote ejb2 sfsb invocation. Not sure, but think it's related to the Remoting upgrade.
> I've attached a JBoss Profiler report showing refs to the leaked classloader. This one's long and complicated, but I think the relevant stuff is right at the start. The MarshalledInvocation seems to be leaking to the input stream and from there into a thread pool.
> I switched my build back to Remoting 2.0.0 and the test passed."

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