[
https://issues.apache.org/jira/browse/LOG4J2-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486516#comment-17486516
]
Simon Ziller commented on LOG4J2-3192:
--------------------------------------
We found the issue. There were some changes loading the ConfigurationSource
Object, which results in
{{"org.apache.logging.log4j.core.config.ConfigurationSource#file"}} is null and
{{ConfigurationFileWatcher}} is not used.
If we don't use URI Format for configuration it works.
{noformat}
NOK: -Dlog4j2.configurationFile=file:log4j.properties
OK : -Dlog4j2.configurationFile=log4j.properties
{noformat}
> log4j2.properties: monitorInterval has no effect since 2.13.2
> -------------------------------------------------------------
>
> Key: LOG4J2-3192
> URL: https://issues.apache.org/jira/browse/LOG4J2-3192
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.14.1
> Reporter: Simon Ziller
> Assignee: Ralph Goers
> Priority: Blocker
> Attachments: Log4j2Test.zip
>
>
> "Properties configuration files support the advertiser, monitorInterval,
> name, packages, shutdownHook, status, and verbose attrbutes." source:
> [https://logging.apache.org/log4j/2.x/manual/configuration.html#Properties]
> But adding "monitorInterval=5" to log4j2.properties seems to have no effect.
> Changes to log4j2.properties do not change the configuration.
> This Problem was already solved with LOG4J2-1263.
> Since the feature was not working with the latest version 2.14.1, I tried
> older versions. The Version 2.13.1 is the last one where monitorInterval is
> working in a property file configuration.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
