cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Petr Nídl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CXF-4529) PermGen Leak for CXFAuthenticator (WS Client Configuration)
Date Mon, 22 Oct 2012 15:14:12 GMT

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

Petr Nídl commented on CXF-4529:
--------------------------------

I agree with Danielius. This is definitely a classloader leak. Although it is caused by design
of java.net.Authenticator class the problem comes from CXF that either should not rely on
java.net.Authenticator or should come with solution that allows its correct cleanup. Also
the workaround mentioned by Freeman (java.net.Authenticator.setDefault(null)) will not work
correctly because it can wipe out all authenticators possibly registered by other (still running)
applications.
                
> 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
>            Assignee: Freeman Fang
>              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