[ https://issues.apache.org/jira/browse/TRINIDAD-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955383#comment-13955383 ]
Arsene Costin commented on TRINIDAD-2465: ----------------------------------------- I browsed the code and I saw that *org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl* could unload correctly the *GlobalConfiguratorImpl* by removing the classloader key from _CONFIGURATORS map > Memory Leak on redeploy > ----------------------- > > Key: TRINIDAD-2465 > URL: https://issues.apache.org/jira/browse/TRINIDAD-2465 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Infrastructure > Affects Versions: 2.1.0-core > Environment: Apache Tomcat version 7.0.52 > Reporter: Arsene Costin > Priority: Critical > > Hello , > I was using Plumbr (https://plumbr.eu/) to test our application for memory > Leaks. > The plumr tool showed me that we have a memory leak when we need to redeploy > our application. > I would like to mention that we keep all of the Trinidad depedencies in > <tomcat_dir>/lib folder (Shared classloader for all webapps) > Here is the memory leak text. > The leaking classloader is being held > in key of java.util.HashMap$Entry > in table of java.util.HashMap > in static _CONFIGURATORS of > org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl > in elementData of java.util.Vector > in classes of > org.apache.catalina.loader.StandardClassLoader > in > org.apache.tomcat.util.net.SocketWrapper > in reference from native code > (JNI local) -- This message was sent by Atlassian JIRA (v6.2#6252)