RE: File system full causes log4cxx to crash

>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

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 full. My solution to use a try/catch works for us for now since we only have a single appender, but as was mentioned below if we decided to add a second appender the try/catch is a ve

RE: File system full causes log4cxx to crash

>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

RE: File system full causes log4cxx to crash

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

RE: File system full causes log4cxx to crash

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

RE: File system full causes log4cxx to crash

>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

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:[EMAIL PROTECTED] Sent: Friday, September 19, 2008 11:46 AM To: Log4CXX User Subject: File system full

File system full causes log4cxx to crash

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 crashe

RE: Building a debug version of log4cxx

It looks like I can do this with this make CXXFLAGS="-g -O0" By default the build uses -O2 and for gdb we need -O0. I think defining this flag will do the trick. From: Peter Steele [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 09, 2008 3:01 PM To: Log4CXX User Subject:

Building a debug version of log4cxx

We've been getting some core dumps in our application that are appear to be occurring in the middle of calls in the log4cxx library. We want to build a debug version of log4cxx for our FreeBSD boxes so we can properly analyze the core dumps with gdb. What's the trick in build a debug version of log

RE: Is this a bug or user error?

s, Inc. www.rubixinfotech.com "Peter Steele" <[EMAIL PROTECTED]> 08/18/2008 10:35 AM Please respond to "Log4CXX User" To "Log4CXX User" cc Subject RE: Is this a bug or user error? A multi-file-appender would be a great

RE: Is this a bug or user error?

rnold [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2008 11:27 AM To: Log4CXX User Subject: Re: Is this a bug or user error? On Aug 15, 2008, at 10:59 AM, Peter Steele wrote: > We use the DailyRollingAppender, defined as follows in our config > file: &g

RE: RollingFileAppender question

ure the appender with Append = true and then trigger a rollover when the application first starts up. You might need a special case when the application starts for the first time if you don't want an extra empty log file, but hope this gets you closer. -Chris ____

Is this a bug or user error?

We use the DailyRollingAppender, defined as follows in our config file: Several applications log to the same log file using this appender. What's happening is when the rollover occurs at midnight, some processes s

RollingFileAppender question

We are using a RollingFileAppender defined as follows: This works the way we want with one exception: When our app that uses this appender starts up it overwrites the existing log file. This is of course because we

RE: Maximum backup index for RollingFileAppender

It would have been nice if some kind of renaming scheme was used that was near zero-cost. For example, a date/time stamp... -Original Message- From: Jostein Tveit [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2008 11:42 PM To: Log4CXX User Subject: Re: Maximum backup index for Rolli

RE: Maximum backup index for RollingFileAppender

Yeah, I guess that makes sense. Thanks for the clarification. -Original Message- From: Dale King [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2008 2:06 PM To: Log4CXX User Subject: Re: Maximum backup index for RollingFileAppender On Wed, Jul 16, 2008 at 4:33 PM, Peter Steele

Maximum backup index for RollingFileAppender

We use a RollingFileAppender defined as follows: It works fine, except that the maxBackupIndex appears to top out at 13, even though we have 20 specified. Are we doing something wrong or is 13 a hard coded maximum f

Microsecond timestamps

Does the ConversionPattern parameter support microsecond timestamps?

RE: How to set a FileAppender to STDOUT?

>In Java, stdout is normally accessed using a console appender. Why are you using this construct in the first place? In the end it looks that we're not going to need to do this after all so it is a moot point... Peter

RE: Using the syslog appender in log4cxx

>Any luck with this? I will post the full configuration files for syslog and >log4cxx as well as my sample program if it might help. No, I never did get LOCAL7 to work

RE: How to set a FileAppender to STDOUT?

Wednesday, June 11, 2008 4:09 PM To: Log4CXX User Subject: Re: How to set a FileAppender to STDOUT? Peter Steele wrote: > Changing to ConsoleAppender isn't an option in our case unfortunately... > Would you mind sharing why it's not an option? I just see the ends of writing to

RE: How to set a FileAppender to STDOUT?

>Here's my un-magic invocation: > > Changing to ConsoleAppender isn't an option in our case unfortunately... Thanks for the reply...

How to set a FileAppender to STDOUT?

What do I need to specify in the File parameter to mean STDOUT? I have this: ... which works in log4j but this just creates a file called System.out in log4cxx. What's the magic formula?

RE: Setting log file name dynamically

("MyApp"); setenv("logfile.name", "MyApp.log", 1); Very simple! David On Mon, 2008-06-09 at 11:38 -0700, Peter Steele wrote: I am using the following code to set the log file dynamically instead of defining it in the xml file: DOMConfigurator::configure(conf

Setting log file name dynamically

I am using the following code to set the log file dynamically instead of defining it in the xml file: DOMConfigurator::configure(config); LoggerPtr logger = Logger::getLogger(cat_name); FileAppenderPtr appender = logger->getAppender("FILE"); Pool p; a

RE: Using the syslog appender in log4cxx

>I was able to get local7 to work on 0.9.7 using a simple logging test program >(a.out) and the syslog appender snippet I included earlier. I added a local7 >configuration line to my syslog.conf and reloaded that. Did you specify "LOCAL7" as the facility in the config file?

Is it safe to has different processes on the same machine log to the same file?

This is what we're doing right now and it appears to be working fine. Is this safe to do though, as a general rule?

RE: Using the syslog appender in log4cxx

>That is a bug in version 0.10.0 Local 2 and higher was not implemented >correctly. See this difference to see the cut-and-paste error: > > > >It has already been fi

RE: Using the syslog appender in log4cxx

prefer to have log4cxx send log messages to the same LOCAL7 log file that we use for our Java apps. Any suggestions on how to accomplish this? -Original Message----- From: Peter Steele [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 6:30 AM To: Log4CXX User Subject: RE: Using the sys

RE: Using the syslog appender in log4cxx

>While this version is no longer supported by the developers, the following >syslog appender works on my Debian systems running 0.9.7: Thanks for the xml snippet, I'll give this a try. And we may very well upgrade to the latest version, but we have 65+ machines with 0.9.7 so it's a bit of a job t

Using the syslog appender in log4cxx

We have a multi-host, multi-application product and want to use syslog to collect logs in one location. For our Java apps, I just had to add the code to the log4j config file to enable our Java apps to use the syslog throug