You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2022/06/27 07:03:00 UTC

[jira] [Commented] (LOG4J2-3540) ConfigurationScheduler should respect the configured Clock for scheduling

    [ https://issues.apache.org/jira/browse/LOG4J2-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17559026#comment-17559026 ] 

Ralph Goers commented on LOG4J2-3540:
-------------------------------------

A plan for this needs to be discussed on the dev mailing list before anything is committed. This is a big deal.

> ConfigurationScheduler should respect the configured Clock for scheduling
> -------------------------------------------------------------------------
>
>                 Key: LOG4J2-3540
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3540
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Configuration, Core
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>            Priority: Major
>
> ConfigurationScheduler uses a ScheduledExecutorService which defaults to using the wall clock. When the configured Clock isn't a SystemClock or SystemMillisClock, then the scheduler should be overridden with one that decorates scheduled tasks to respect the clock. This will help in speeding up and otherwise exercising tests related to configuration scheduling and cron expressions.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)