[
https://issues.apache.org/jira/browse/LOG4J2-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200846#comment-16200846
]
ASF GitHub Bot commented on LOG4J2-2036:
----------------------------------------
GitHub user cakofony opened a pull request:
https://github.com/apache/logging-log4j2/pull/115
[LOG4J2-2036] CompositeConfiguration supports Reconfiguration
Regression was introduced by the fix for LOG4J2-1912.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cakofony/logging-log4j2 LOG4J2-2036
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/115.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #115
----
commit 9bb0496cdef96a043c493e90d5df582b402a1afa
Author: Carter Kozak <c4kof...@gmail.com>
Date: 2017-10-11T19:43:50Z
[LOG4J2-2036] CompositeConfiguration supports Reconfiguration
Regression was introduced by the fix for LOG4J2-1912.
----
> CompositeConfiguration with monitorInterval fails to reload full configuration
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-2036
> URL: https://issues.apache.org/jira/browse/LOG4J2-2036
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.9.0
> Environment: I have pushed a very simple repro here:
> https://github.com/cakofony/log4j2-composite-config-repro
> Reporter: Carter Douglas Kozak
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
