[
https://issues.apache.org/jira/browse/LOG4J2-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457968#comment-15457968
]
Steffen Offermann commented on LOG4J2-1548:
-------------------------------------------
I just forked Log4j2, created a new branch called {{release-2.6.x}}, updated
all versions in the {{pom.xml}} to 2.6.3-SNAPSHOT, and applied the patches. I
had to omit one part related to {{ResolverUtil.java}}, as that file has changed
in the current {{master}}-Branch, but that did not affect the test cases, i.e.
all Log4J2 test cases ran successfully:
https://github.com/sofax/logging-log4j2.git
(even though it took ages :) )
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 .................................... SUCCESS [0.213s]
[INFO] Apache Log4j API .................................. SUCCESS [7.654s]
[INFO] Apache Log4j Core ................................. SUCCESS [7:30.729s]
[INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [3.750s]
[INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [2.553s]
[INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [1.461s]
[INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [1.468s]
[INFO] Apache Log4j Flume Bridge ......................... SUCCESS [3:25.483s]
[INFO] Apache Log4j Web .................................. SUCCESS [2.128s]
[INFO] Apache Log4j Tag Library .......................... SUCCESS [9.423s]
[INFO] Apache Log4j JMX GUI .............................. SUCCESS [0.638s]
[INFO] Apache Log4j Samples .............................. SUCCESS [0.030s]
[INFO] Apache Log4j Samples: Flume - Common .............. SUCCESS [0.658s]
[INFO] Apache Log4j Samples: Flume - Remote .............. SUCCESS [0.746s]
[INFO] Apache Log4j Samples: Flume - Embedded ............ SUCCESS [1.562s]
[INFO] Apache Log4j Samples: Configuration ............... SUCCESS [1.177s]
[INFO] Apache Log4j Samples: LoggerProperties ............ SUCCESS [1.259s]
[INFO] Apache Log4j BOM .................................. SUCCESS [0.100s]
[INFO] Apache Log4j NoSQL ................................ SUCCESS [1.632s]
[INFO] Apache Log4J Performance Tests .................... SUCCESS [8.151s]
[INFO] Apache Log4j Streaming Interface .................. SUCCESS [4.283s]
[INFO] Apache Log4j JUL Adapter .......................... SUCCESS [6.001s]
[INFO] Apache Log4j Liquibase Binding .................... SUCCESS [1.255s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:52.831s
[INFO] Finished at: Fri Sep 02 10:46:48 CEST 2016
[INFO] Final Memory: 42M/629M
[INFO] ------------------------------------------------------------------------
{noformat}
> [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
> 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: [email protected]
For additional commands, e-mail: [email protected]
