You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Matt Hogstrom (JIRA)" <ji...@apache.org> on 2006/11/14 22:52:39 UTC
[jira] Updated: (GERONIMO-1142) Thread in RMI Runtime ThreadGroup
occasionally keeps stale MultiParentClassLoader alive
[ http://issues.apache.org/jira/browse/GERONIMO-1142?page=all ]
Matt Hogstrom updated GERONIMO-1142:
------------------------------------
Fix Version/s: Verification Required
(was: 1.2)
Not sure if this is still relevant
> Thread in RMI Runtime ThreadGroup occasionally keeps stale MultiParentClassLoader alive
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-1142
> URL: http://issues.apache.org/jira/browse/GERONIMO-1142
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Memory Leaks
> Affects Versions: 1.0, 1.0-M5
> Environment: Win XP/Sun JDK 1.4.2
> Reporter: Kevan Miller
> Priority: Minor
> Fix For: Verification Required
>
>
> Occasionally after a deploy/undeploy of DayTrader. A Thread will keep a stale instance of MultiParentClassLoader from being GC'ed. The chain of references is as follows:
> java.lang.Thread.inheritedAccessControlContext -->
> java.security.AccessControlContext.context -->
> java.security.ProtectionDomain[4] -->
> java.security.ProtectionDomain.classLoader -->
> org.apache.geronimo.kernel.config.MultiParentClassLoader
> The Thread is a member of the RMI Runtime ThreadGroup.
--
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