Re: [log4perl-devel] Message Duplication

[<Msc...@ao...>]

In a message dated 1/7/03 10:31:08 AM Pacific Standard Time, 
mra...@ci... writes:

> As the log level for the CCBU.Patch is set to ERROR, I would expect (even if 
> the logger decides to fire for a WARN message from CCBU.Patch.Ticket ), 
> appender for the CCBU.Patch not pickup the WARN message that is started 
> from CCBU.Patch.Ticket. So eventually there should be just one WARN message 
> for CCBU.Patch.Ticket and CCBU.Patch should ignore WARN log as it is below 
> the log level set for its appender?

That's exactly the catch with Log4j. Once one logger has decided that the 
message is going to be logged, it is forwarded to all appenders 
*unconditonally* (except, of course, appender thresholds have the last word). 
In your example, this means that CCBU.Patch won't run any checks once 
CCBU.Patch.Ticket has already decided to fire. That's a concept that's, 
admittedly, sometimes confusing -- but well established in the log4j 
community.

-- Mike
Mike Schilli
log...@pe...