Martin,
> In a nutshell, I want to configure two different appenders, let's say a
> DB appender and a file appender. One of them would be active by
> default, but the user could switch to the other, referring to it by name
> as specified in the props, without having to create
Mark,
In a nutshell, I want to configure two different appenders, let's say a
DB appender and a file appender. One of them would be active by
default, but the user could switch to the other, referring to it by name
as specified in the props, without having to create a new
appender from sc
Martin,
> Unfortunately there doesn't seem to be a provision for programmatic
> access to _all_ Appenders, e.g. those configured in a
> PropertyConfigurator. In fact PropertyConfigurator _clears_ the list of
> appenders and is proud of it.
What other appenders would there be?
Hi,
I want to allow interactive changes to the log4j configuration, e.g.
using a web interface. Log4J allows access to Loggers all right,
And through Loggers I can obtain the list of _used_ Appenders.
Unfortunately there doesn't seem to be a provision for programmatic
access to _all_ Appe
gzilla/show_bug.cgi?id=10185
AsyncAppender.close() does not call close() on attached appenders
--- Additional Comments From [EMAIL PROTECTED] 2002-06-24 17:25 ---
I wrote to the log4j-dev mailingn list the other day and received the following
reply back from Ceki:
"You are correct
gzilla/show_bug.cgi?id=10185
AsyncAppender.close() does not call close() on attached appenders
Summary: AsyncAppender.close() does not call close() on attached
appenders
Product: Log4j
Version: 1.2
Platform: Other
OS/Version:
Hello,
I have recently looked at the org.apache.log.output.io.rotate package
of Avalon LogKit. Their implementation is cleaner and more flexible than
our own RollingFileAppender or the DailyRollingFileAppender.
With the upcoming enhancement in the log4j config language we will
be able to suppor
=Bush"
You can find the archives at
http://marc.theaimsgroup.com/?l=log4j-user&r=1&w=2 and
http://marc.theaimsgroup.com/?l=log4j-dev&r=1&w=2
-Jim Moore
-Original Message-
From: Gary Udstrand [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 04, 2002 7:28 PM
To: log4
I am writing my own appender and would like to pass in some options. I am not
sure that I quite understand the mechanism that is to be used to do this, can someone
give me a point in the right direction? I apologize if this has been asked and
answered in previous dialogues but I was unab
Perfect. Thank you
-Original Message-
From: Ceki Gulcu [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 12, 2001 1:11 AM
To: Log4J Developers List
Subject: Re: Appenders
The throwable (exception) information is contained within the event. See
the getThrowableInformation() and
Is there a recommended way to handle exceptions that may be thrown by an
appender ?
It looks like the standard exception handling is to report an error using
the OnceOnlyErrorHandler - which reports an error once and then ignores
future exceptions.
Would the right technique be to overide methods
The throwable (exception) information is contained within the event. See
the getThrowableInformation() and getThrowableStrRep methods in the
org.apache.log4j.spi.LoggingEvent class. HTH, Ceki
At 21:05 11.12.2001 -0800, you wrote:
>I have an TextAppender working.
>
>I extend AppenderSkeleton
I have an TextAppender working.
I extend AppenderSkeleton and override append( LoggingEvent ... ). This works great.
However I would like to
be able to get a hold of the Exception Object in my appender, when calling something
like:
catch( Exception e )
{
m_log.error( "My Err
can you reproduce this?
Are you 100% certain that your disk is not full?
-Original Message-
From: Abhijat Thakur [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 15, 2001 9:19 PM
To: [EMAIL PROTECTED]
Subject: Appenders MaxBackUpIndex
Hi,
I am sorry to send this problem to
Hi,
I am sorry to send this problem to developer mailing list but the thing is
that this is a weird problem that i am having and it might be a bug about
which i am not sure. I have a logging.properties file that looks something
like whats shown below. What happens is that when it makes 20 back u
Hi,
I have a logging.properties file that looks something like whats shown
below. What happens is that when it makes 20 back up files of agenda.log in
the next run (i.e 21st) it wipes out all the 20 back up files of agenda.log
and after that it dumps all messages in one file and keeps overwriting
What a waste of time. The threshold option does what you want.
At 18:52 04.10.2001 +0200, you wrote:
>> Hi Log4J development team
>>
>> We did need to log to the NT eventlog and a file (our own log), through
>> the same category. Yes, that is not a problem because you just add the
>> FileAppen
Also see PriorityFilter class.
> -Original Message-
> From: Jon Skeet [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 04, 2001 12:02 PM
> To: LOG4J Developers Mailing List
> Subject: RE: Adding a Priority to the Appenders.
>
>
> > > But now all
> > But now all priorities (assuming that the priority for
> > category is DEBUG)
> > will be logged both in the file and in the NT eventlog. Our
> > requirements
> > state that only log messages with the priority FATAL should
> > be logged to
> > the NT eventlog and all should be logged to the
> Hi Log4J development team
>
> We did need to log to the NT eventlog and a file (our own log), through
> the same category. Yes, that is not a problem because you just add the
> FileAppender class and the NTEventLogAppender class.
>
> But now all priorities (assuming that the priority for cate
Title: Where can I find more info on Appenders.
Haven't used it personally, but off the download page on the Log4J site,
you can get info on the JDBC appender.
http://jakarta.apache.org/log4j/docs/download.html
This
will probably do what you want.
Steven
-Original Message
Title: Where can I find more info on Appenders.
Hi there,
I would like to now if there is place where I can find more information on how to extend appenders. I'm trying to create an appender that writes to a database table. If there is an appender that already does that, I wou
bject: Regarding Log File size and logging different messages to
> differe nt appenders.
>
>
>
> Hi,
> I was looking on the log4j API and wanted help on two questions.
>
> Regarding logging the messages after reading from an XML file :
> 1. how can we restrict the
way performance wise.
2. Also i want to log different messages to different Appenders. For example
say 3 appenders - console, file and NTEventLog and I wanna log debug and
info to console, info and warning to file and Error and fatal messages to
NTEventLog then how do we organise these things with
24 matches
Mail list logo
