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 2015/09/10 20:19:46 UTC

[jira] [Created] (LOG4J2-1119) Disable JMX by default

Remko Popma created LOG4J2-1119:
-----------------------------------

             Summary: 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: Blocker
             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] {{sun.rmi.dgc.server.gcInterval}}.

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
(v6.3.4#6332)

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