[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    RE: Chainsaw's internal logging
From:       <asgeir.nilsen () telenor ! com>
Date:       2004-06-17 7:11:22
Message-ID: 72A1D96D00C9A34989BEE17B983E762E094907 () TNS-FBU-2E-006 ! corp ! telenor ! no
[Download RAW message or body]

True, the iternal logging is of varying quality.

However, there seems to be SOME interesting things flying past Chainsaw's \
stdout/stderr (or Web Start's console / log).

In particular, SAX errors and warnings, and one annoying NPE I very much would like \
to get to the bottom of, appears when I use XMLSocketReceiver..

Asgeir

> From: Paul Smith [mailto:psmith@apache.org]
> Sent: Tuesday, June 15, 2004 12:26 AM
> 
> Unfortunately Chainsaw's own internal logging is very 
> inconsistent at the 
> moment, and there isn't much one can do about it at the moment. :(
> 
> Do you need to really need Chainsaw's internal logs yourself?
> 
> cheers,
> 
> Paul Smith
> 
> On Fri, 11 Jun 2004 asgeir.nilsen@telenor.com wrote:
> 
> > Hello all,
> > 
> > Chainsaw logs all its internal log4j events to stdout, 
> > which appears in the Java Web Start Console (or a log file 
> > configured from Web Start).
> > 
> > I have been trying to create an XML file for Chainsaw's 
> > Automatic Configuration which redirects these events into 
> > Chainsaw itself.
> > 
> > However, none of my attempts have been successful.  Using a 
> > FileAppender, I managed to log all the events Chainsaw 
> > received *externally* to a file, but none of the internal events.
> > 
> > How should one do this?
> > 
> > Asgeir

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]