[
https://issues.apache.org/jira/browse/LOG4J2-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280652#comment-17280652
]
Ralph Goers commented on LOG4J2-3001:
-------------------------------------
There are so many permutations already in the rolling appenders that I am
reluctant to add even more. This would really complicate things since there
would have to be a flag to indicate whether rolling happens before or after
since checking in both places would cause massive problems. I should note
though, that the tirggering you are referring to only happens when the
TimeBased or Size Based Triggering Policies are used. The CronTriggeringPolicy
kicks off the rollover on a separate thread.
> Support rollover after appending event
> --------------------------------------
>
> Key: LOG4J2-3001
> URL: https://issues.apache.org/jira/browse/LOG4J2-3001
> Project: Log4j 2
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.14.0
> Reporter: Stamatis Zampetakis
> Priority: Major
>
> Rollover actions are triggered based on a LogEvent and the rollover if
> necessary is performed before appending the actual log event. Currently, it
> is not possible to first append the log event and then perform the rollover
> if necessary. In some situations it is necessary to have finer control on
> when the rollover is performed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
