[
https://issues.apache.org/jira/browse/LOG4J2-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047935#comment-13047935
]
Ralph Goers commented on LOG4J2-43:
-----------------------------------
I have a suspicion the previous comment is for Log4J 1.x?
I expect a programmatic call will be required to ultmately allow the rollover
via JMX. However, it would also make sense to be able to provide configurable
guidance on when a rollover must be forced.
> Allow DailyRollingFile appender to rollover programmatically
> -------------------------------------------------------------
>
> Key: LOG4J2-43
> URL: https://issues.apache.org/jira/browse/LOG4J2-43
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders
> Reporter: Lukasz Wielek
> Priority: Minor
>
> Allow DailyRollingFile appender to rollover programmatically without
> appending any new log event.
> This will allow log file rollover, in case there's no messages to be logged
> for a long time,
> but the current log file needs to be backed up.
> I think making the rollOver method public would be sufficient :)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
