logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-1119) Disable JMX by default
Date Thu, 10 Sep 2015 23:37:46 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Remko Popma updated LOG4J2-1119:
    Priority: Critical  (was: Blocker)

Changed priority to "Critical" since there is a workaround: users can disable JMX with the
property {{log4j2.disable.jmx}}.

I wish I had named that property {{log4j2.enable.jmx}} now, and considered renaming it (while
supporting the old name as well) but I concluded the confusion it would cause outweighs the
aestetics. So I'll keep the current name but change the default value.

> Disable JMX by default
> ----------------------
>                 Key: LOG4J2-1119
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1119
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: JMX
>    Affects Versions: 2.3
>            Reporter: Remko Popma
>            Assignee: Remko Popma
>            Priority: Critical
>             Fix For: 2.4
> I recently learned that RMI will by default trigger a full GC every hour.
> See [Oracle RMI docs|http://docs.oracle.com/javase/7/docs/technotes/guides/rmi/sunrmiproperties.html]
> Since JMX uses RMI, and Log4j 2 by default enables JMX, we are unintentionally causing
all applications that use Log4j 2 to do a full GC every hour.
> This is clearly undesirable. 
> I propose we change to switch JMX off by default and update the documentation to reflect
this change and the reason behind it.

This message was sent by Atlassian JIRA

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

View raw message