You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/09/12 00:06:20 UTC
[jira] [Assigned] (LOG4J2-1548) [CronTriggeringPolicy]
ConfigurationScheduler schedules the task infinitely after first fire
[ https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma reassigned LOG4J2-1548:
-----------------------------------
Assignee: Gary Gregory
> [CronTriggeringPolicy] ConfigurationScheduler schedules the task infinitely after first fire
> --------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1548
> URL: https://issues.apache.org/jira/browse/LOG4J2-1548
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2
> Reporter: Pierrick HYMBERT
> Assignee: Gary Gregory
> Priority: Blocker
> Fix For: 2.7
>
> Attachments: LOG4J2-1548-testcase-2.patch, LOG4J2-1548-testcase-cleanFoldersRule.patch, LOG4J2-1548-testcase.patch, LOG4J2-1548.patch
>
>
> After first fire at fixed time, rename/archive action is sheduled infinitely.
> Example of configuration:
> {code:xml}
> <RollingFile name="RollingFile"
> fileName="target/rolling-cron-once-a-day/rollingtest.log"
> filePattern="target/rolling-cron-once-a-day/rollingtest-%d{yyyyMMdd}_%d{HHmmss}-%i.log.gz"
> immediateFlush="true">
> <PatternLayout pattern="%d %p %C{1.} [%t] %m%n" />
> <CronTriggeringPolicy schedule="27 58 13 * * ?"/>
> </RollingFile>
> {code}
> First trigger is scheduled at 13:58:27 then every new log entry generates an archive file.
> Test case and suggested fix attached.
--
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