All, I have a webapp that uses Axis 1.4 as client. I see few ThreadLocal forcible removed error messages in tomcat log file during undeploy process of the application which suggests me that there exists some kind of memory leak due to the way certain ThreadLocals are handled by Axis 1.4. Here are error messages. I was looking into the mailing list archives and could not obtain any conclusive solution to address this issue. I am wondering how I can track and clean up these threadlocals from my application if Axis is not already has a fix for this.
------------------------------------------------------------------ SEVERE: A web application created a ThreadLocal with key of type [org.apache.axis.utils.XMLUtils.ThreadLocalDocumentBuilder] (value [org.apache.axis.utils.xmlutils$threadlocaldocumentbuil...@2316537e]) and a value of type [org.apache.xerces.jaxp.DocumentBuilderImpl] (value [org.apache.xerces.jaxp.documentbuilderi...@ec38731]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [org.apache.axis.utils.XMLUtils.ThreadLocalDocumentBuilder] (value [org.apache.axis.utils.xmlutils$threadlocaldocumentbuil...@1ee3bfc2]) and a value of type [org.apache.xerces.jaxp.DocumentBuilderImpl] (value [org.apache.xerces.jaxp.documentbuilderi...@1ee90696]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. ------------------------------------------------------------------- Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
