You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2008/09/16 15:08:09 UTC
DO NOT REPLY [Bug 45816] Not able to change Threshold level of any
appender
https://issues.apache.org/bugzilla/show_bug.cgi?id=45816
Jacob Kjome <ho...@visi.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Jacob Kjome <ho...@visi.com> 2008-09-16 06:08:09 PST ---
This is a question about usage, not a bug in Log4j. Please use the Log4j-user
list for questions like this, not Bugzilla. Below is a response from Bender
Heri from the Log4j-dev list. Marking bug invalid.
"The level of the logger is considered first when issuing a log call.
Only if this barrier can be passed the level of each appender is
consulted. If your logger defines INFO, then DEBUG entries never pass
this filter."
Jake
--
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