[jira] [Resolved] (LOG4J2-1202) Remove use of the ConfigurationMonitor in favor of the WatchManager

["Ralph Goers (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-1202.
---------------------------------
       Resolution: Fixed
         Assignee: Ralph Goers
    Fix Version/s: 2.5

Fix has been committed to master.

> Remove use of the ConfigurationMonitor in favor of the WatchManager
> -------------------------------------------------------------------
>
>                 Key: LOG4J2-1202
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1202
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Ralph Goers
>            Assignee: Ralph Goers
>             Fix For: 2.5
>
>
> Currently the ConfigurationMonitor is called during each log event to determine whether the configuration file has changed. The actual check is only done periodically but there is some overhead to determine if the check should be performed.
> The FileWatcher runs as a scheduled task. As such, monitoring the configuration file will remove the overhead of calling the ConfigurationMonitor on each log event.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org