[
https://issues.apache.org/jira/browse/LOG4J2-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-2526.
---------------------------------
Resolution: Won't Fix
This is impractical at best and impossible at worst. "Polling" all registered
lookups periodically to see if any of the ways they might have been configured
to detect changes isn't possible since we have no idea how they might have been
configured. Lookups are also transitory. Once they are called they effectively
disappear. So even if they had a way of notifying the LoggerContext that they
had changed they aren't even around to check.
> Log4j2 should monitor changes to lookup values
> ----------------------------------------------
>
> Key: LOG4J2-2526
> URL: https://issues.apache.org/jira/browse/LOG4J2-2526
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Reporter: Bhavesh Patel
> Priority: Minor
>
> Log4j2 monitor changes made directly to the log4j configuration file. There
> is currently no mechanism to reconfigure if any lookup value has changed.
> Log4j2 should monitor look up value changes.
> An example of this use would be the following
>
> From log4j2.xml, if we do a bundle lookup to a property file
> (<property_file_name>.properties) and get the value thats used by the log4j2
> configuration we should be monitoring any changes made to he lookup value
> external to the log4j configuration file.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
