logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Alaev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-426) Permgen leak: Log4j2 does not unregister MBeans on shutdown
Date Tue, 15 Oct 2013 04:32:42 GMT

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

Sergey Alaev commented on LOG4J2-426:
-------------------------------------

I didn't test it, but it looks like MBean names are hard-coded and therefore there can't be
different MBeans for multiple contexts in single JVM.

> 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


Mime
View raw message