cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Freeman Fang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-4529) PermGen Leak for CXFAuthenticator (WS Client Configuration)
Date Thu, 11 Oct 2012 09:43:03 GMT

    [ https://issues.apache.org/jira/browse/CXF-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473999#comment-13473999
] 

Freeman Fang commented on CXF-4529:
-----------------------------------

Hi,

In my option it's not a memory leak,  per the code in
java.net.Authenticator
// The system-wide authenticator object.  See setDefault().
    private static Authenticator theAuthenticator;
It's system-wide object, so it's intended behavior to not gc, and this code is out of CXF
code base, CXF can't change this behavior.
BTW, when you use 
java.net.Authenticator.setDefault(null);
it cause system-wide effect so it may affect other module which need use this  theAuthenticator.

Anyway, it shouldn't be a CXF issue

Freeman
                
> PermGen Leak for CXFAuthenticator (WS Client Configuration)
> -----------------------------------------------------------
>
>                 Key: CXF-4529
>                 URL: https://issues.apache.org/jira/browse/CXF-4529
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration, JAX-WS Runtime
>    Affects Versions: 2.6.1
>         Environment: Apache Tomcat 7, Windows 7 32bit
>            Reporter: Holger Sunke
>              Labels: leak, permgen
>
> Hello,
> seemes to me there is a memory leak with the CXFAuthenticator. There is a static reference
to it in java.net.Authenticator.theAuthenticator .
> This prevents the GC from collecting the WebappClassLoader on hot undeployment.
> I helped myself by doing 
> java.net.Authenticator.setDefault(null);
> on contextDestroy().
> Our web application uses CXF as a jasWS client configured with Spring 3.0.5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message