I am in the process of making some major modifications to log4cxx which I hope to get the initial commit in a few days. When reviewing RollingFileAppender, it does appear that it will have to be almost rewritten. I've stubbed it out in my working copy at the moment.

What is troubling is that the unit tests did not pick this up. Either there are not unit tests in the log4j suite that test this behavior or they were not ported to log4cxx. It would be helpful if you could review the RollingFileAppender unit tests (if any) in the log4j CVS and write any necessary tests and submit them as a bug report to log4j through their Bugzilla. If you do that, then I can pick them up and port them to log4cxx.


On Dec 6, 2004, at 11:52 AM, Veeraraghavan, Sedhu K. wrote:

Hi
Using log4j to rollover the file when it reaches the specified
size. Rollover happens well and good. When one jvm writes logs using
log4j, other process filter opens the handle to the file and reads. When
the filter starts reading the file when file reaches the max size, the
rolled over file is not there.
Either not created, deleted or truncated. So basically we are
loosing the old logs.


please help in addressing the issue.

thanks
-Sedhu




Reply via email to