[jira] [Commented] (LOG4J2-426) Permgen leak: Log4j2 does not unregister MBeans on shutdown

["Jon Larry (JIRA)" <ji...@apache.org>]

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

Jon Larry commented on LOG4J2-426:
----------------------------------

I'm not getting uniquely registered jmx LoggerContext either. Added log4jContextName and log4jConfiguration context-params in  web.xml and am using org.apache.logging.log4j.core.web.Log4jServletContextListener servlet-listener of two different web apps.
(version 2.0-beta9)

Resulting in a single LoggerContext Mbean:
.  org.apache.logging.log4j2:type=LoggerContext,ctx=AsyncLoggerContext

Also the mbean attributes for the AssyncLoggerContext are incorrect:
.   configLocation=file:/Applications/eclipse-cequint/Eclipse.app/Contents/MacOS/CCDB
.   configText=FileNotFoundException...

I would have expected the configLocation to reflect the log4j2 file that was loaded and configText to contain the xml in that file.





> Permgen leak: Log4j2 does not unregister MBeans on shutdown
> -----------------------------------------------------------
>
>                 Key: LOG4J2-426
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-426
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 2.0-beta9
>         Environment: JDK7 64bit, Win8 64bit. Apache Tomcat 7
>            Reporter: Sergey Alaev
>
> Subj. This causes permgen leak on undeploying web applications which uses log4j2.
> Also, as far as i can see, there is no support exposing multiple log4j2 contexts via JMX which can be nice for web applications.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org