[LOG4J2-2036] CompositeConfiguration with monitorInterval fails to reload full configuration

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.9.0
• Component/s: Configurators

Environment

I have pushed a very simple repro here:
https://github.com/cakofony/log4j2-composite-config-repro

• Assignee: Unassigned
• Reporter: Carter Kozak
• Created: 07/Sep/17 15:59
• Updated: 03/Apr/18 15:50
• Resolved: 03/Apr/18 15:49

Description

Steps to reproduce:

1. Create two configuration files, in my case I use a "default" embedded configuration on the classpath, and a second configuration on disk for overrides (this configuration uses monitorInterval=30).

2. Configurator.initialize(null, classLoader, ImmutableList.of(defaultUri, diskUri), null)

3. On initial startup, the two configurations are merged perfectly, everything works as expected.

4. Modify the on disk (override) configuration while the application is running, the failure is most apparent if I update a logger to reference an appender only defined in the "default" configuration. Reconfiguration executes but only using the file on disk, as though the first configuration has disappeared.

This is a regression from 2.8.2, so I have rolled back to that version. Unfortunately 2.8.2 is affected by LOG4J2-1912 and complains with misleading warning messages so I've had to update the status logger to error level from info.

Issue Links

• links to: GitHub Pull Request #115