Hi, > There was no concern expressed about the log files that are currently not > rolled (generally, I suspect, because well written apps won;t trigger content > to those files).
We do have concerns about rotate the output to stdout/stderr. In most of our cases, this is due to logging framework conflict between log4j and logback in a web application. The default behavior is that all the logging content are eventually gone to catalina.out. Most of the users even won't be aware of it, until being alerted by running out of the disk space (The web application may run for months). To avoid this, we actually have implemented a feature in Tomcat to rotate catalina.out on a daily basis. Under the hood we use a customized PrintStream to replace System.out/System.err, capture the content, and output to JULI. Since it is rotated by day, it make us easier to keep the latest N files. I know the best solution will be solving the conflict, but according to our experience, most of the user don't know there is a conflict. In there any interest in adding this feature to Tomcat? ------------------------------------------------------------------ From:bugzilla <bugzi...@apache.org> Time:2017 Jun 6 (Tue) 03:45 To:dev <dev@tomcat.apache.org> Subject:[Bug 61105] Roll log files by default https://bz.apache.org/bugzilla/show_bug.cgi?id=61105 --- Comment #2 from Mark Thomas <ma...@apache.org> --- The conversation at TomcatCon was around putting a (relatively large) limit on the number of files that are kept by default. Picking a number of of thin air, how does 90 days sound? There was no concern expressed about the log files that are currently not rolled (generally, I suspect, because well written apps won;t trigger content to those files). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
