Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/115
@garydgregory The fix you provided also seems broken, after a couple
reloads I'm seeing:
```
java.lang.NullPointerException
--
at
org.apache.logging.log4j.core.config.composite.DefaultMergeStrategy.mergConfigurations(DefaultMergeStrategy.java:139)
at
org.apache.logging.log4j.core.config.composite.CompositeConfiguration.setup(CompositeConfiguration.java:122)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:235)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:249)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:545)
at
org.apache.logging.log4j.core.LoggerContext.onChange(LoggerContext.java:667)
at
org.apache.logging.log4j.core.config.ConfiguratonFileWatcher$ReconfigurationRunnable.run(ConfiguratonFileWatcher.java:68)
at java.lang.Thread.run(Thread.java:748)
```
Also, if factory.getConfiguration returns null, currentConfig is left null
instead of currentConfig.
---
