You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2010/01/19 17:50:54 UTC
[jira] Resolved: (CXF-2624) Classloader leakage in
org.apache.cxf.common.util.ASMHelper.LOADER_MAP
[ https://issues.apache.org/jira/browse/CXF-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2624.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.6
2.1.9
Assignee: Daniel Kulp
> Classloader leakage in org.apache.cxf.common.util.ASMHelper.LOADER_MAP
> ----------------------------------------------------------------------
>
> Key: CXF-2624
> URL: https://issues.apache.org/jira/browse/CXF-2624
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.1.5
> Reporter: Daniel Feist
> Assignee: Daniel Kulp
> Fix For: 2.1.9, 2.2.6
>
> Attachments: WeakIdentityHashMap.java.patch
>
>
> See: http://old.nabble.com/Classloader-leakage-when-using-JAXB-binding-in-appServer-td26101445.html
> This map continues to have reference to classes generated and used by the now undeployed webapp meaning the webapp classloader never goes away.
> The implementation of this map although weak is not weak enough, because if a entry references a key (it seems to) then the key although it is a WeakReference never goes away and therefore neither does the entry (the classloader).
> See the "implementation note" 2/3 of the way through the javadoc here: http://java.sun.com/j2se/1.5.0/docs/api/java/util/WeakHashMap.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.