[
https://issues.apache.org/jira/browse/CXF-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Feist updated CXF-2624:
------------------------------
Attachment: WeakIdentityHashMap.java.patch
Patch for WeakIdentityHashMap.java that resolve the problem described in the
user list thread by taking into account 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
> 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
> 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.
