Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.5
-
None
-
Advanced
Description
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.