[
https://issues.apache.org/jira/browse/CXF-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622184#comment-13622184
]
Daniel Kulp commented on CXF-4529:
----------------------------------
The ReferencingAuthenticator is not loaded from the same classloader as the
rest of CXF, its now from a ClassLoader which uses the system classloader as
the parent. Thus, the "leak" is very minimal (single byte[] class) as it
doesn't hold onto all the CXF classes. Also, once the real authenticator
(CXFAuthenticator class) is gc'd, a call into the system authenticator may
start a process of removing themselves (although that process looks slightly
wrong. (need to double check that).
In anycase, as far as we're concerned, it's "fixed" as well as we can. If
someone has a patch that can provide a better solution, feel free to submit it
and we'll consider it.
> 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: Daniel Kulp
> Labels: leak, permgen
> Fix For: 2.7.1
>
>
> 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
