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

List:       log4j-user
Subject:    RE: Why won't initialization accept trace?
From:       Ceki =?iso-8859-1?Q?G=FClc=FC?= <ceki () qos ! ch>
Date:       2002-06-25 18:52:21
[Download RAW message or body]


Given your config file, I don't see how logs could be lost. By default, the 
FileAppender and its subclasses flush the output buffer after each append 
operation. Thus,  events can't be "lost". Your config file does not change 
this default behavior. (You don't set the ImmedateFlush option to false or 
BufferIO option to true.)

I am tempted to say that it is common-logging related problem but that is 
probably not true either. In the absence of further information, the most 
probably cause is that the events are not generated in the first place. Are 
you sure the log statements are really called before the program exists?

At 11:23 25.06.2002 -0500, Steve Cohen wrote:
>Thank you but...
>
>OUCH!  Where did I get the idea that this was a standard level? (or that 
>this ever worked?)  Probably from commons-logging, which I am using on top 
>of log4j.  Stupid.
>
>Guess I need to bone up on custom levels.
>
>Do you have an answer to my second question below?  That's the one that's 
>really giving me problems.
>
>Thanks,
>Steve
>
>-----Original Message-----
>From: Ceki Gülcü [mailto:ceki@qos.ch]
>Sent: Tuesday, June 25, 2002 11:19 AM
>To: Log4J Users List
>Subject: Re: Why won't initialization accept trace?
>
>Trace is not a standard log4j level.
>
>The text Threshold="null" is output by DOMConfigurator to indicate that you
>have not set a hierarchy-wide threshold. The message is terse but otherwise
>harmless.
>
>Are you using a custom Trace level?

--
Ceki


--
To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

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