[ https://jira.jboss.org/jira/browse/JBSEAM-3932?page=com.atlassian.jira.pl... ] Alexander Schwartz updated JBSEAM-3932: --------------------------------------- Description: org.jboss.el.util.ReflectionUtil (from jboss-el) uses a private static ReferenceCache methodCache and this ReferenceCache is leaking a thread that is used for cleanup. You can't call a cleanup method from the outside. Every redeployment of an application will leak one thread due to this bug. And it causes a memory leak as the web application class loader can't be unloaded due to this bug. The pom.xml of jboss-el states "JBoss EL is a extended EL implementation, distributed with Seam", therefore I report this bug against Seam. was: org.jboss.el.util.ReflectionUtil (from jboss-el) uses a private static ReferenceCache methodCache and this ReferenceCache is leaking a thread that is used for cleanup. You can't call a cleanup method from the outside. But the methodCache could be removed from the code as it is not used anyway: it is read in findMethod(), but nothing is stored (the code is commented out in version 1.0_02.CR2, and not present in all other souces (2.0.2.CR1, 2.0.1.GA). Every redeployment of an application will leak one thread due to this bug. And it causes a memory leak as the web application class loader can't be unloaded due to this bug. The pom.xml of jboss-el states "JBoss EL is a extended EL implementation, distributed with Seam", therefore I report this bug against Seam. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3932?page=com.atlassian.jira.pl... ] Alexander Schwartz updated JBSEAM-3932: --------------------------------------- Attachment: reference.patch Suggestion how the thread could be cleaned (plus servletcontextlistener that can be put to web.xml) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3932?page=com.atlassian.jira.pl... ] Matthew Lieder commented on JBSEAM-3932: ---------------------------------------- I just identified this leak too, using YourKit. It's one of a number of issues we've identified that are preventing our webapp's classloader from getting garbage collected during an undeploy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3932?page=com.atlassian.jira.pl... ] Norman Richards updated JBSEAM-3932: ------------------------------------ Fix Version/s: 2.1.2.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3932?page=com.atlassian.jira.pl... ] Matthew Lieder commented on JBSEAM-3932: ---------------------------------------- Confirmed fixed. Only leak left, when using RichFaces 3.3.1-SNAPSHOT which fixes another leak, is an annoying Java2D Disposer thread issue; that's almost certainly not Seam's fault though. Thanks Norman! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira