users
[Top] [All Lists]

Problems with log4j Threshold (log4j 1.2.9)

To: users@xxxxxxxxxx
Subject: Problems with log4j Threshold (log4j 1.2.9)
From: steve.gutter@xxxxxxxxxx
Date: Mon, 22 Aug 2005 13:34:58 -0400
Delivered-to: mailing list users@cinjug.org
Mailing-list: contact users-help@cinjug.org; run by ezmlm
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.


<Prev in Thread] Current Thread [Next in Thread>
  • Problems with log4j Threshold (log4j 1.2.9), steve . gutter <=