[
https://issues.apache.org/jira/browse/LOG4J2-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752989#comment-15752989
]
Gary Gregory commented on LOG4J2-1740:
--------------------------------------
I do not think you _always_ want to have the start of a scheduler create a
thread pool as this would be wasteful for set ups that do not need this
feature. The AbstractConfiguration class always holds a sheduler for example.
> Add CronTriggeringPolicy programmatically leads to NPE
> ------------------------------------------------------
>
> Key: LOG4J2-1740
> URL: https://issues.apache.org/jira/browse/LOG4J2-1740
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.7
> Reporter: Peter Nimmervoll
>
> When i try to add a RollingFileAppender with a CronTriggeringPolicy
> programmatically then I get a NPE because the ScheduledExecutorService in
> ConfigurationScheduler is null. IMO the ScheduledExecutorService should
> always be created even when there are no items which needs to be scheduled.
> Caused by: java.lang.NullPointerException
> at
> org.apache.logging.log4j.core.config.ConfigurationScheduler.schedule(ConfigurationScheduler.java:107)
> ~[log4j-core-2.7.jar:2.7]
> at
> org.apache.logging.log4j.core.config.ConfigurationScheduler.scheduleWithCron(ConfigurationScheduler.java:120)
> ~[log4j-core-2.7.jar:2.7]
> at
> org.apache.logging.log4j.core.appender.rolling.CronTriggeringPolicy.initialize(CronTriggeringPolicy.java:72)
> ~[log4j-core-2.7.jar:2.7]
> at
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.initialize(RollingFileManager.java:104)
> ~[log4j-core-2.7.jar:2.7]
> at
> org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender.createAppender(RollingRandomAccessFileAppender.java:218)
> ~[log4j-core-2.7.jar:2.7]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
