Reputation: 2285
I have my log4j2.xml config file set to be checked every 30 seconds:
<Configuration status="WARN" monitorInterval="30">
...
</Configuration>
Is it possible to programmatically tell log4j2 to check for changes in the configuration instead of having a timeout?
N.B. I don't want to programmatically load the configuration specifying the config file, I just want to tell log4j2 to check the config file that has been loaded before as if the monitorInterval expired.
Thanks!
Upvotes: 27
Views: 22142
Reputation: 21390
What about org.apache.logging.log4j.core.config.Configurator.reconfigure()
?
Upvotes: 0
Reputation: 737
What about using org.apache.logging.log4j.core.config.Configurator
?
LoggerContext loggerContext = LoggerContext.getContext(false);
final Configuration configuration = loggerContext.getConfiguration();
Configurator.reconfigure(configuration);
Upvotes: 2
Reputation: 36844
There is currently no clean way to do this. It can be done with reflection. (Of course this may break if the implementation changes.)
UPDATE: this is wrong. There is a clean way, see jamp's answer below.
org.apache.logging.log4j.core.LoggerContext ctx = (org.apache.logging.log4j.core.LoggerContext) LogManager.getContext(false);
org.apache.logging.log4j.core.config.FileConfigurationMonitor mon = (org.apache.logging.log4j.core.config.FileConfigurationMonitor) ctx.getConfiguration().getConfigurationMonitor();
// use reflection to get monitor's "nextCheck" field.
// set field accessible
// set field value to zero
mon.checkConfiguration();
Upvotes: 5
Reputation: 2285
It looks like I've found the solution:
((org.apache.logging.log4j.core.LoggerContext) LogManager.getContext(false)).reconfigure();
Does anyone see anything wrong/side-effects with this?
Upvotes: 33