[jira] [Updated] (CXF-4529) PermGen Leak for CXFAuthenticator (WS Client Configuration)

["Holger Sunke (JIRA)" <ji...@apache.org>]

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

Holger Sunke updated CXF-4529:
------------------------------

    Description: 
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.

  was:
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.

    
> 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