On Mon, Sep 22, 2008 at 1:10 AM, Adam Woods <[EMAIL PROTECTED]> wrote:
>
>
> Also, there does not seem to be any APIs in LoggingEvent which allow you
> to insert into the MDC.
>
>
MDC is local to the thread, not the logging event. The API to interact with
the MDC are the static methods on the log4
On 2008-09-20 11:37, Peter Steele wrote:
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
>Looking at FileOutputStream::write in svn head I see that if
apr_file_write
>doesn't return APR_SUCCESS, it throws an IOException with the write
call's
>status. I am not familar enough with the code to see who/what should
catch that,
>but to work like 0.9.7 I'd expect it to be caught at some ap
On 2008-09-22 17:03, Peter Steele wrote:
We're using 0.9.7 in fact, under FreeBSD. Our case is bit more
Maybe we need to catch this IOException in our wrapper functions?
The IOException was in the 0.10.x code. I didn't see any exception around the
writing to files in 0.9.7. As near as I cou
On 2008-09-19 15:31, Jacob L. Anawalt wrote:
heartedly. This discussion and some recent tweaking of a mail service's
log rotation (via logrotate) on one server motivated me to figure out
how to make this work.
I have implemented this in my multi-threaded application by blocking all signals
Okay, thanks, I'll give it a try.
-Original Message-
From: Jacob L. Anawalt [mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2008 4:24 PM
To: Log4CXX User
Subject: Re: File system full causes log4cxx to crash
On 2008-09-22 17:03, Peter Steele wrote:
> We're using 0.9.7 in fact, unde
