cxf-issues mailing list archives

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

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

nihongye commented on CXF-4529:
-------------------------------

but in CXFAuthenticator 
{code}
 Class<?> cls = loader.loadClass(ReferencingAuthenticator.class.getName());
                Authenticator auth = (Authenticator)cls.getConstructor(Authenticator.class,
Authenticator.class)
                    .newInstance(instance, wrapped);
{/code}
“newInstance(instance, wrapped)” param instance is load by webappclassloader,so the webappclassloader
is refence from the system classloader

> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message