You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/25 23:03:38 UTC

[jira] [Resolved] (CXF-4006) Possible classloader leak due to ThreadLocal

     [ https://issues.apache.org/jira/browse/CXF-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved CXF-4006.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6
                   2.5.3
                   2.4.7
         Assignee: Sergey Beryozkin

Sorry I did not catch the issue earlier; definitely fixed now, a temp regression spanning last 1-2 releases on 2.4.x/2.5.x
The leak should be more or less negligible, but the way to eliminate it with the released CXFs is to register a simple JAXBElementProvider (or/and JSONProvider) only which will override setMessageContext method and make it no-op. 

MessageContext is needed to check for custom STAX handlers and may be Marshaller properties. This all can be managed in the custom provider using PhaseInterceptorChain.getCurrentMessage().

thanks
                
> Possible classloader leak due to ThreadLocal
> --------------------------------------------
>
>                 Key: CXF-4006
>                 URL: https://issues.apache.org/jira/browse/CXF-4006
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.5.1
>         Environment: Glassfish
> OpenJDK Runtime Environment (IcedTea6 1.10.4) (fedora-61.1.10.4.fc16-x86_64)
>            Reporter: Art O Cathain
>            Assignee: Sergey Beryozkin
>             Fix For: 2.4.7, 2.5.3, 2.6
>
>
> org.apache.cxf.jaxrs.ext.MessageContextImpl is kept in a ThreadLocal for each HTTP request which means when a CXF-servlet-based webapp is undeployed, the webapp's classloader leaks. 
> (At least, I think that's what's going on, I'm not that expert at tracking down memory leaks. Perhaps I have misconfigured something?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira