TimeBasedRollingPolicy doesn't roll if the date change happens when the
application is not currently running
------------------------------------------------------------------------------------------------------------
Key: LBCORE-64
URL: http://jira.qos.ch/browse/LBCORE-64
Project: logback-core
Issue Type: Bug
Components: Rolling
Affects Versions: unspecified
Environment: Windows, JSE6
Reporter: Gamaliel Amaudruz
Assignee: Logback dev list
Priority: Minor
I discovered the same. I've been using log4j for years and it behaves
differently than logback in this context, it will roll the log
according to the configuration regardless of the execution context,
which is imho a better behavior. I hope it would be possible to fix
this issue or at least give an option between the two behaviors.
Here is how I use it:
- I have a monitoring task that is run every ten minutes and lasts
for a dozen of seconds. I set logback to roll the logs everyday but
it never happens because logback rolls ONLY if it is running while
the date changes. I end up with a very huge log file that never rolls.
Log4j will roll it during the first new execution after the date has
changed.
More info: http://www.qos.ch/pipermail/logback-user/2008-October/000626.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://qos.ch/mailman/listinfo/logback-dev
