Probably a limit you can configure with your shell. In bash it's ulimit
-c unlimited to get full core dumps and ulimit -a
to see the settings (0 bytes by default on my shell.) It and gdb might
not be helpful anyway if your log4cxx library is
stripped of debugging symbols. If you do pursue getting
in the right direction.
-Original Message-
From: Peter Steele [mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2008 5:46 PM
To: Log4CXX User
Subject: RE: File system full causes log4cxx to crash
Okay, thanks, I'll give it a try.
-Original Message-
From: Jacob L. Anawalt
Jacob L. Anawalt [EMAIL PROTECTED] writes:
I am glad it worked out for you. At the same time I am concerned that
you had to do this and I didn't. I would like to reproduce the problem
so that I can handle it, preferably without putting try/catch around
every logging statement...
Some time
to
Log4CXX User log4cxx-user@logging.apache.org
To
Log4CXX User log4cxx-user@logging.apache.org
cc
Subject
Re: File system full causes log4cxx to crash
Jacob L. Anawalt [EMAIL PROTECTED] writes:
I am glad it worked out for you. At the same time I am concerned that
you had to do this and I
:26 PM
Please respond to
Log4CXX User log4cxx-user@logging.apache.org
To
Log4CXX User log4cxx-user@logging.apache.org
cc
Subject
RE: File system full causes log4cxx to crash
I’ll add my own agreement to this. It’s not acceptable for a logger to
crash an application when the volume becomes
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
Does not one have any comments on this? Surely someone must have
experienced this scenario, specially the volume where logs are being
recorded becoming filled up.
From: Peter Steele [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2008 11:46 AM
To: Log4CXX User
Subject: File system full
To
Log4CXX User log4cxx-user@logging.apache.org
cc
Subject
RE: File system full causes log4cxx to crash
Does not one have any comments on this? Surely someone must have
experienced this scenario, specially the volume where logs are being
recorded becoming filled up.
From: Peter Steele [mailto
