Hi, I got problems while using the DailyRollingFileAppander. I have some questions about this appander:
Question: Why is it using an intermediate file for writing the current messages and rename the file while rollover? Reason: I use a multi process application logging to the same file (necessary and not my decision). This prevents the rollover of the file because of multiple open filehandles. The file is truncated while each process executes the rollover handling. A second problem is the explanation of the intermediate log file to customers using a product with this appander. I need to use a file name and date pattern like: Filename: "<hostname>-error-" Datepattern: "yyyy-MM-dd'.log'" Do create result files like "zeus-error-2002-01-15.log" files. But the current log (before rollover) file looks like "zeus-error-". This does not look very professional. :( Workaround: I created a custom version of the rolling file appender. This version writes to the final log file name (multiple processes are possible) and creates one new file while rolling over. Is anyone interessted to use this code as default behavior of the DailyRollingFileAppander? Improvements: - do not use members of the parent class as an improvement - does not need extra file system operations while rolling over (file deletion and rename) Disadvantage: - changes behavior in relation to the current version Any comments are welcome. Klaus -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
