[
https://issues.apache.org/jira/browse/CXF-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-2625.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.6
2.1.9
Assignee: Daniel Kulp
Fixed for 2.2.6 as we changed the CachedContextAndSchemas to hold onto the
JAXBContext using a weak reference. That was holding onto the Class objects
which prevented it from being cleaned out.
> Class-loader leakage in org.apache.cxf.jaxb.JAXBDataBinding.JAXBCONTEXT_CACHE
> ------------------------------------------------------------------------------
>
> Key: CXF-2625
> URL: https://issues.apache.org/jira/browse/CXF-2625
> 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
>
>
> See:
> http://old.nabble.com/Classloader-leakage-when-using-JAXB-binding-in-appServer-td26101445.html
> Here is appears we have another map the maintains references to the generated
> classes and in turn to the webappClassloader that is no more expect this one
> doesn't even try to be weak. I notice there is a clearCaches() method but
> i'm unsure about using that at anytime in runtime because even though i'm
> taking down one cxf Service there may be user services alive using jaxb at
> the same time.
> I don't have a patch for this one currently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
