|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
_______________________________________________ logback-dev mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-dev
entry.timestamp looks to refer to the last time it was used-- which of course a logging event would force an update. The SiftingAppender documentation states:
With the current implementation any additional logging events would extend that linger window for 10 seconds from the last event. This would seem like a reasonable implementation as forcing a close just because the 10 seconds expired even if we're continuing to receive logging events for that appender would very likely cause us to immediately open the file back up.
Your adminlog isn't being closed due to LOGBACK-940.