As Dan told me 2 days ago, you should use the keyword Threshold in your appender. This will fix the problem.
Christophe Marcourt Mondeca Ingénieur R&D 3, Cité Nollez. 75018 Paris Phone : +33 1 44 92 35 03 Mobile : +33 6 14 48 65 66 Fax : +33 1 44 92 02 59 http://www.mondeca.com/fr ICQ : #119811844 -----Message d'origine----- De : Ortloff Alexander [mailto:[EMAIL PROTECTED]] Envoyé : mercredi 20 novembre 2002 15:41 À : '[EMAIL PROTECTED]' Objet : Why do ancestor loggers ignore level? Hi, we've had the same problem as described by Adam Hardy in thread http://www.mail-archive.com/log4j-user@jakarta.apache.org/msg05667.html "Can't control logging via root - get all msgs despite setting priority". I still don't feel this behaviour be plausible. If levels are not inherited but assigned to loggers, why don't ancestor loggers check their level before printing a forwarded log request? Example: log4j.rootLogger=ERROR, A1 log4j.logger.myDefinedLogger=DEBUG, A2 >From my point of view, myDefinedLogger.info("just an info msg"); should print in A2 but not in A1 since ERROR > INFO > DEBUG. Nevertheless, it prints in both A1 and A2. From my point of view this violates the basic selection rule (as stated in "Short introduction to log4j"). What's the idea behind? ......................................... Mit freundlichem Gruß / With kind regards Alexander Ortloff Siemens AG Transportation Systems Rail Automation System Development TS RA SD 16 Ackerstr. 22 D-38126 Braunschweig Germany Fon: +49 531 226 2536 Fax: +49 531 2277 2536 MailTo:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
