[jira] [Commented] (LOG4J2-3571) Continue archiving after JVM restart

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

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

Ralph Goers commented on LOG4J2-3571:
-------------------------------------

I think an Action could handle this. PRs are welcome.

> Continue archiving after JVM restart
> ------------------------------------
>
>                 Key: LOG4J2-3571
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3571
>             Project: Log4j 2
>          Issue Type: Improvement
>    Affects Versions: 2.18.0
>            Reporter: Wolff Bock von Wuelfingen
>            Priority: Minor
>
> Currently, when a log file gets rolled over and is (for example) zipped, and a power loss / jvm close happens during zipping, after the jvm comes back up the old files are left untouched.
> It would be much nicer if log4j would scan the directory for all pattern matching files and see if a pair of log and zip (or whatever archive format) files exists. For example:
> {code:java}
> system2022-08-11 09.41.10.log.zip
> system2022-08-11 09.41.10.log{code}
> And simply continues or restarts archiving.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)