[
https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739962#comment-14739962
]
Remko Popma commented on LOG4J2-1119:
-------------------------------------
I think I acted too quickly here. The java runtime itself also registers MBeans
for memory and CPU management and a few more. That by itself doesn't cause
hourly GCs. It is not the act of registering MBeans that starts the RMI server;
you need to specify additional startup options for that.
I will revert the changes I made for this Jira ticket. Sorry for the false
alarm.
I will add a note to the JMX page that users should be aware of the GC
behaviour of the default RMI transport.
> 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]
