logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46248] Log4j content is empty
Date Thu, 20 Nov 2008 06:31:29 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46248


Curt Arnold <carnold@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #1 from Curt Arnold <carnold@apache.org>  2008-11-19 22:31:28 PST ---
Usage questions should be asked in log4j-user.  Marking as invalid.

The line:

log4j.logger.Level=DEBUG

sets the threshold of the logger named "Level" to debug.  Unless the logger
that you used is named "Level" or a descendant ("Level.foobar", etc), then the
WARN threshold set on the root logger will take precedent.  You do not show how
the variable "logger" in initialized in your testing code, but I'm guessing it
does not look like:

Logger logger = Logger.getLogger("Level");


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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


Mime
View raw message