[ http://jira.jboss.com/jira/browse/JBAS-5270?page=all ] Adrian Brock closed JBAS-5270. ------------------------------ Resolution: Rejected Assignee: (was: Scott M Stark) Your test application does NOT show a classloader leak. I tried deploying/undeploying it and running jhat and yes it does show your classes still around. But this is not a memory leak. The reason they are still there is because Sun's java.lang.reflect.Proxy contains a WeakHashMap which holds a reference to the $Proxy classes in its ReferenceQueue in its "loaderToCache" instance field. i.e. it is ready to be garbage collected They are still in the ReferenceQueue because a WeakHashMap only clears up things lazily, i.e. next time you access it. When I deploy another EJB, it will create new proxies which will access the WeakHashMap and clears the old reference. e.g. 1) I deploy a completely different EJB, your classes disappear from the dump 2) If I redeploy your EJB, the old classes are no longer visible and neither is the old classloader This cannot be the cause of a permenant generation exhaustion unless your permenant generations is too small to survive a single redeploy of your application. i.e. it is nearly full before the redeploy Most likely your leak (I wouldn't describe it as orphaned since somebody is still referencing it), if there is one, is caused by static singletons in your code or thirdparty code you use. e.g. certain apache commons projects are notorious for causing this problem, or you have some other application deployed still referencing classes from the undeployed application But please, do not discuss this further here, use the forums to ask for help unless you can show an org.jboss.* class as a strong reference to an undeployed classloader/class. Your example just shows a JDK class holding a WeakReference that is ready to be reaped. -- 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