Hi. I'm not sure if this is a bug. It seems simple enough that it's probably either supposed to work this way or it's a config error on my end (though I can't find it)
Consider: root logger set to level DEBUG, logging to console logger A set to level ERROR, logging to A.log logger A.B set to level DEBUG, logging to B.log B.log contains everything A.B received. That's correct, but A.log contains DEBUG messages from A.B even though it is set to only accept ERRORS or higher. Further, the root logger receives the DEBUG messages from A.B even though you'd think A would have filtered them. It would appear that level checking only occurs at the entry logger, not at every logger on up the heirarchy. A cursory glance at the source code seems to support this, though I could be wrong. If it's supposed to be this way, then I think we lose a benefit of logger hierarchies: The ability for subclasses to log heavily during development while not spamming the logs of their more-mature parents. Can someone shed some light on this? Thank you, Daniel Hannum ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions Health Services Corporation and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you -- To unsubscribe, e-mail: <mailto:log4j-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:log4j-dev-help@;jakarta.apache.org>
