AW: set additivity in log4j properties file

Try the following: log4j.additivity.=false Regards Thomas > -Ursprüngliche Nachricht- > Von: Bin Ji [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 19. Februar 2002 05:54 > An: Log4J Users List > Betreff: set additivity in log4j properties file > > > Hi, > > Can I set the additivity a

set additivity in log4j properties file

Hi, Can I set the additivity attribute of categories in log4j property file? I know I can do it in java code, but it will be very convenient if we can do it in property file too. Thanks, Bin -- To unsubscribe, e-mail: For additional commands, e-mail:

base category name?

Is it possible to set a base category name? i.e., in my code I create categories for "foo" and "foo.bar", for the webapp "project-a", but what I want logged is for them to appear as "project-a.foo" and "project-a.foo.bar" This way I can filter (in Chainsaw) based on the base category of the w

RE: Attaching appenders to root

Switching to the 1.2beta3 jar appears to have solved the problem. This is the output for 1.2beta 3 log4j: Parsing for [root] with value=[DEBUG, stdout, R]. log4j: Level token is [DEBUG]. log4j: Category root set to DEBUG log4j: Parsing appender named "stdout". log4j: Parsing layout options for "st

RE: Attaching appenders to root

Put the propertie file in the classpath. I think this will solve the problem. -Original Message- From: Adam Krieg [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 3:33 PM To: 'Log4J Users List' Subject: RE: Attaching appenders to root 2 additional lines were printed out: log4

RE: Attaching appenders to root

Hmm, looks like you are using log4j 1.1.3. Correct? At 18:33 18.02.2002 -0500, you wrote: >2 additional lines were printed out: > >log4j: Could not find root category information. Is this OK? >log4j: Finished configuring. > >I noticed "debug" was lower case in my config file. I changed it to >

RE: Attaching appenders to root

2 additional lines were printed out: log4j: Could not find root category information. Is this OK? log4j: Finished configuring. I noticed "debug" was lower case in my config file. I changed it to uppercase, but the results were the same. -Original Message- From: Ceki Gülcü [mailto:[EM

Re: Attaching appenders to root

Adam, Try adding the following line to see what the PropertyConfigurator does with your config file: #Add this line log4j.debug=true log4j.rootLogger=debug, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.

Attaching appenders to root

I know this question is in the FAQ, but the explanation is a little unclear as to how to resolve this problem. I'm trying to run the example seen in the manual and I'm getting log4j: No appenders could be found for category (ma.bridge.jdbc.MyApp). I see that this as an item in the FAQ, but my

Announcing log4j 1.2beta3

Greetings, I am pleased to announce log4j 1.2beta3. In addition to many performance improvements, bug fixes, and other small enhancements, log4j 1.2 beta3 adds JMX support, Mapped Diagnostic Contexts, and buffered IO capability. One important change is the replacement of the Category class with L

Re: survey: Is the FATAL priority level useful?

On Mon, Feb 18, 2002 at 05:08:15PM -0500, Cakalic, James wrote: > Were you aware of the log4py project on sourceforge? > http://sourceforge.net/projects/log4py/ Jim, Yes, I have looked briefly at log4py. Log4py is a little limited for what I would like to see in the Python core. It is a minimal p

Re: survey: Is the FATAL priority level useful?

On Mon, Feb 18, 2002 at 11:16:51PM +0100, Ceki Gülcü wrote: > Trent, > > The following quote is from the log4j book I am currently writing. You might > find the quote useful. Thanks, Ceki! That is helpful. Trent -- Trent Mick [EMAIL PROTECTED] -- To unsubscribe, e-mail:

RE: survey: Is the FATAL priority level useful?

I don't agree that the FATAL priority level is useless. > A FATAL problem is typically just > an uncaught > exception -- and if the exception is uncaught there > really seems no > appropriate to actually *log* the problem. Anything that causes the app to shut down should be logged, so that the

RE: survey: Is the FATAL priority level useful?

Were you aware of the log4py project on sourceforge? http://sourceforge.net/projects/log4py/ Jim > -Original Message- > From: Trent Mick [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 18, 2002 3:52 PM > To: [EMAIL PROTECTED] > Subject: survey: Is the FATAL priority level useful? >

Re: survey: Is the FATAL priority level useful?

Trent, The following quote is from the log4j book I am currently writing. You might find the quote useful. It is not always easy to decide when to use which level. In fact, a decision needs to be made on each logging statement - that is on countless occasions. To ease the pain of deciding, log4j

RE: survey: Is the FATAL priority level useful?

Trent, The FATAL is just part of the anachronistic set of labels which are attached to Priorities (levels). At Cognos we have abandoned the old UNIX labels as completely unhelpful and simply work with an ordered set of values which can be used either to denote the severity level or the detail lev

SocketServer and Filters?

From what I read it appears that a SocketServer can not user Filters because the SocketServer uses the PropertyConfigurator anf Filters can only be loaded from the DOMConfigurator. Am I correct? Is there a way to get the SocketServer to use the DOMConfigurator? Thanks Mark -- To unsubsc

survey: Is the FATAL priority level useful?

Hello, I am currently specing out a core logging module for the Python language which borrows from log4j. I would like to know if, in practice, people have found the FATAL priority level of use in a language with exception handling support. The way I see it (not having the benefit of experience

Re: Centralized Logging class and the State of Log4J

At 15:55 18.02.2002 -0500, Adam Krieg wrote: >I'm considering using Log4J for a new project, but have some questions about >it that I need to be answered before I make my decision. I'm interested in >having a single logging class that client classes can call just by writing: > >MyLogger.debug(thi

Centralized Logging class and the State of Log4J

I'm considering using Log4J for a new project, but have some questions about it that I need to be answered before I make my decision. I'm interested in having a single logging class that client classes can call just by writing: MyLogger.debug(this,"log statement"); I'm passing in a reference to

Multiple configuration files

Hi log4j experts, Im a new on log4j technology. So please help me with a problem. Im trying to read multiple configuration files for logging events in mulitiple LOG files. However Im not able to do so... Please respond asap. Regards, Manoj Rathod -- To unsubscribe, e-mail:

RE: JDK1.4

Jon Certainly be v.interested in what you find out -- Rob Send reply to: "Log4J Users List" <[EMAIL PROTECTED]> Subject:RE: JDK1.4 Date sent: Mon, 18 Feb 2002 18:53:05 - From: "Jon Skeet" <[EMAIL PROTECTED]> To: "Log4

RE: JDK1.4

> Not specifically Log4J related, but worthy of note. > > I'd strongly suggested anyone considering moving up to JDK1.4 > take a long hard > look at the following bug (and hopefully vote it up the priority list) > > http://developer.java.sun.com/developer/bugParade/bugs/4523761.html > > I'm l

JDK1.4

Not specifically Log4J related, but worthy of note. I'd strongly suggested anyone considering moving up to JDK1.4 take a long hard look at the following bug (and hopefully vote it up the priority list) http://developer.java.sun.com/developer/bugParade/bugs/4523761.html I'm lost for words how S

categoryFactory in XML format?

Greetings, I have made a subclass of the class Category (I'd like to override the Fatal method of category). I am currently using an XML configuration file. My question is how can I put the following line: log4j.categoryFactory = org.apache.log4j.examples.MyCategoryFactory in XML-format in my

RE: Jboss/Tomcat weapps and different log4j

I am not using the jboss log mbean, I am using it from different webapps and hence the web.xml contains the path to the log4j properties and the init method in my servlet initializes the logging. But because the jboss ships with log4j.jar the individual classloader with the webapps does not create

Re: Jboss/Tomcat weapps and different log4j

Log4j added support for multiple hierarchies in Application Servers. The actual implementation is the responsibility of the Application Server. As of this writing JBoss has not added the necessary support pending the official release of log4j 1.2. Regards, Ceki At 17:52 17.02.2002 -0500, you

Re: Log4j vs. New JDK 1.4 Logging API

The pages are still there but intentionally not linked. Here are the URLs: http://jakarta.apache.org/log4j/docs/srtw.html http://jakarta.apache.org/log4j/docs/critique.html At 09:16 18.02.2002 -0600, you wrote: >I've been digging through the documentation for the new JDK 1.4 from Sun and

Log4j vs. New JDK 1.4 Logging API

I've been digging through the documentation for the new JDK 1.4 from Sun and I noticed there is a new logging API. There used to be a discussion on the Log4j web site comparing Log4j to the new logging API from Sun. I've just gone through every link on the main page of the Log4j web site and I ca

changing the level of a complete logger-hierarchy

i want to change a complete logger-hierarchy to a specific level. so all sub-loggers should have the same level too. this should be done without modifying config-files. example: starting situation: level of logger "package1.class1" == DEBUG level of logger "package1.package2.class1" == INFO Then

Re: Log4J 1.1.3 problem Reply ASAP Please

The resolution to your first issue is to use the configureAndWatch(...) method of the PropertyConfigurator or DOMConfigurator class. It will configure logging based on the values in the specified config file and, if/when values change in that config file, reconfigure based on the new values. Or