[
https://issues.apache.org/jira/browse/CXF-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-3758.
------------------------------
Resolution: Fixed
Fix Version/s: 2.4.3
Assignee: Daniel Kulp
I couldn't reproduce this at all. The patch should also not be necessary as
where ever we set the threadlocal, we have a clear call in a finally block to
make sure the local is kept clear. I did find one location where, in the
finally, there was other code preceding it that, if it errors, could leave the
thread local set. I've gone ahead and fixed that.
> when web container be redeployed WebServiceContextImpl's static atrribute
> ThreadLocal<MessageContext> may not be release successfully.
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-3758
> URL: https://issues.apache.org/jira/browse/CXF-3758
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.4.2
> Environment: tomcat
> Reporter: qiu zhan bo
> Assignee: Daniel Kulp
> Labels: api-change
> Fix For: 2.4.3
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> when I redeploy cxf application in tomcat 7,I found some log indicate that
> ThreadLocal<MessageContext> object may not be release successfully，When I
> implements GenericServlet's destroy method as follows：
> @Override
> public void destroy() {
> WebServiceContextImpl.clear();
> }
> this bug been fixed。
> there may be some other resources not be destroy as above。
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
