[
https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma reopened LOG4J2-1119:
---------------------------------
I just saw your message now. I do prefer a positive name as well (users can
enable it now by saying disable=false , a double negative...).
I suppose if we internally still support the old property name but in our
documentation only mention the new property name we can do this. And if both
are specified the new property name wins.
> 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]
> {{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: [email protected]
For additional commands, e-mail: [email protected]
