[jboss-jira] [JBoss JIRA] (AS7-6967) ClassLoader memory leak with JSF
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Mon Apr 22 09:21:55 EDT 2013
[ https://issues.jboss.org/browse/AS7-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jaikiran pai updated AS7-6967:
------------------------------
Assignee: Stan Silvert
Component/s: JSF
> ClassLoader memory leak with JSF
> --------------------------------
>
> Key: AS7-6967
> URL: https://issues.jboss.org/browse/AS7-6967
> Project: Application Server 7
> Issue Type: Bug
> Components: JSF
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Vlad Arkhipov
> Assignee: Stan Silvert
> Priority: Critical
> Attachments: war-leak.tar.gz
>
>
> JSF application's classes are not unloaded properly when undeployed. The test case is in the attachment. Steps to reproduce:
> # mvn package
> # deploy war-leak.war
> # open http://localhost:8080/war-leak
> # undeploy war-leak.war
> # analyze a heap dump to find unloaded ModuleClassLoader of war-leak.war
> References to the WAR classes are hold by java.beans.Introspector caches. It seems to be a known bug (feature?). For example Tomcat automatically invokes java.beans.Introspector.flushCaches() when WAR undeploys. There is also IntrospectorCleanupListener in Spring for the same purpose.
> http://wiki.apache.org/commons/Logging/UndeployMemoryLeak
> http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/web/util/IntrospectorCleanupListener.html
--
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
More information about the jboss-jira
mailing list