You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2006/12/20 22:11:21 UTC

[jira] Closed: (GERONIMO-2644) Fix leaking ClassLoaders

     [ http://issues.apache.org/jira/browse/GERONIMO-2644?page=all ]

Kevan Miller closed GERONIMO-2644.
----------------------------------

    Resolution: Invalid

This doesn't seem to be a Geronimo problem.

I'm not seeing any Classloader memory leaks when I run Geronimo on java version "1.5.0_10-b02" running on a Linux box.

I do see Classloader memory leaks running on java full version 1.5.0_06-64 on Mac OS. The JVM is keeping Classloader instances alive. It seems there have been some bugs in the Java 5 runtime. I believe once the Mac OS Java 5 runtime is brought up to a more current service level, these problems will go away.


> Fix leaking ClassLoaders
> ------------------------
>
>                 Key: GERONIMO-2644
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2644
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 1.2, 2.0-M1
>            Reporter: Kevan Miller
>         Assigned To: Kevan Miller
>             Fix For: 1.2, 2.0-M1
>
>
> Looks like we're leaking ClassLoaders. If you deploy/undeploy an app the ClassLoader(s) created for the app are not being GC'ed. Eventually, you'll run out of PermGen space. I assume that this is also causing the PermGen problems when running tests. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira