DO NOT REPLY [Bug 10560] - DailyRollingAppender does not roll each period

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10560>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10560

DailyRollingAppender does not roll each period





------- Additional Comments From david.corbett@suncorpmetway.com.au  2002-11-05 23:45 -------
I have a similar problem occurring (using version 1.1.1). The daily rollover 
time that is specified for my log is midnight and the application server has an 
auto restart at 2 a.m. everyday. The log file specified for the appender is 
called egi.log and I have a DatePattern='.'yyyy-MM-dd.  

If there is no log activity between midnight and the restart at 2 a.m. then the 
previous days log activity will not rollover into a new log with a name of 
egi.log.yyyy-MM-dd (corresponding to the previous days date) but will remain in 
egi.log. If there is no log activity again the next day between midnight and 
the 2 a.m. restart then the same thing will happen again. No data is lost, but 
several days (or more) logging can end up in the one log file. When the file 
does eventually get rolled over (due to midnight to 2 a.m. activity) the 
several days worth of log activity remains in the newly created egi.log.yyyy-MM-
dd file. This behaviour seems contrary to comments made on 2002-07-08 21:28 
('all logging output will be placed in the correct files according to their 
date').

It would appear that an egi.log.yyyy-MM-dd file only gets created when there is 
some log activity between midnight and the 2 a.m. application server restart.

Is this behaviour due to be fixed in a future 1.2 or 1.3 release?

Thanks,

David

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>