IIRC, additivity controls whether the log messages are
propagated to the appenders for ancestors.
So you would need additivity.log4j.com.Alpha.Beta=false
or some such thing to prevent upward propagation of log
messages which happens by default otherwise.
HTH,
~ amol
> -----Original Message-----
> From: steve.gutter@xxxxxxxxxx [mailto:steve.gutter@xxxxxxxxxx]
> Sent: Monday, August 22, 2005 1:35 PM
> To: users@xxxxxxxxxx
> Subject: [cinjug-users] Problems with log4j Threshold (log4j 1.2.9)
>
>
>
> I'm getting some unexpected results with log4j.
>
> I have three loggers set up:
> logger com.Alpha.Beta is set to level = INFO
> logger com.Alpha is set to level = FATAL
> rootLogger is set to level = DEBUG
>
> When I log a level=INFO message to logger com.Alpha.Beta,
> the log message gets written to its ancestor's log (com.Alpha)
> even though com.Alpha's level is FATAL.
>
> It appears as if it doesn't care about ancestry levels once
> its decided to
> write the message to a log: if the log specified meets the
> level criteria
> of the
> message, the message goes to the logger's ancestor's,
> regardless of the ancestor's level.
>
>
> ---------
> You may unsubscribe from this mailing list
> by sending a blank email addressed to:
> users-unsubscribe@xxxxxxxxxx
>
> --
> Find additional help by sending a blank email
> addressed to:
> users-help@xxxxxxxxxx
>
|