You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2013/10/15 02:20:44 UTC
[jira] [Resolved] (LOG4J2-426) Permgen leak: Log4j2 does not
unregister MBeans on shutdown
[ https://issues.apache.org/jira/browse/LOG4J2-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma resolved LOG4J2-426.
--------------------------------
Resolution: Duplicate
Sergey, thank you for reporting this issue. It turns out this one is already on the to-do list (LOG4J2-406) so we are aware of it. I'm closing this one as a duplicate, but you can "watch" issue LOG4J2-406 (that's a JIRA feature) so you get emails when there's any change.
> 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