>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 gettin
On 2008-09-23 11:21, Peter Steele wrote:
/mnt: write failed, filesystem is full
terminate called after throwing an instance of
'log4cxx::helpers::IOException'
what(): IO Exception : status code = 28
Abort trap: 6 (core dumped)
I'm stumped here. The only places I see an IOException thrown in
ot; <[EMAIL PROTECTED]>
09/23/2008 01:26 PM
Please respond to
"Log4CXX User"
To
"Log4CXX User"
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 become
catch is a very big hammer, potentially preventing the other
appender from running. Still, it's better than the application crashing
on us.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 23, 2008 10:20 AM
To: Log4CXX User
Subject: Re: File system full causes l
>I wonder if the difference might be in our iostreams libraries.
>Would you mind debugging the exception and sharing who's throwing it
and why?
My C++ Unix debugging skills aren't great (I'm a Windows guy normally).
I don't gdb or any of the other Unix debuggers. The error I get when I
don't have
"Log4CXX User"
To
"Log4CXX User"
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 didn
"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 t
On 2008-09-23 06:16, Peter Steele wrote:
With 0.9.7 your app threw and exception and aborted when the log volume
filled up. Putting a try/catch around the log call prevented the crash.
I put the same try/catch in my wrapper functions and that worked as
well, so that's all there was to it. I like
ng me 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
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
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
>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-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
respond to
"Log4CXX User"
To
"Log4CXX User"
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: P
I have a couple of comments:
1. The RollingFileAppender allows you to know a priori exactly how much
disk space is required. Is there an amount of space you can be sure will
exist? Worst case, if you own the environment, you could create a
partition and log there.
2. I think a default beha
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
16 matches
Mail list logo
