We've experienced several cases of our logging volume becoming full
during the course of execution of our application. What we would like to
happen in this case is simply to lose any log further messages that are
written after the file system becomes full, but what happens instead is
log4cxx crashes and brings down our application. We're using the
RollingFileAppender on a Unix box. Is there some way to configure
log4cxx to behave a little less drastically in a case like this?
Ideally, the best behavior in a case like this would be for log4cxx to
delete the oldest backup log file and continue logging, but even simply
suspending logging would be better than a crash. Any suggestions?
