logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorbjørn Ravn Andersen <thunderax...@gmail.com>
Subject Re: additivity attribute for logger does not diffrently for root and user-defined logger.
Date Thu, 03 Jul 2008 13:37:51 GMT
Camer38 skrev  den 03-07-2008 15:15:
> Instead I got an log4j warning:
> log4j:WARN No appenders could be found for logger
> (curam.tools.upgradehelper.util.SQLStatements).
This sounds like your configuration file is not picked up.  Try running 
with -Dlog4j.debug=true to see what is happening.

> What is the  meaning of the attribute "additivity" for each logger?
 From http://logging.apache.org/log4j/1.2/manual.html

"*Appender Additivity*

    The output of a log statement of logger /C/ will go to all the
    appenders in /C/ and its ancestors. This is the meaning of the term
    "appender additivity".

    However, if an ancestor of logger /C/, say /P/, has the additivity
    flag set to |false|, then /C/'s output will be directed to all the
    appenders in /C/ and it's ancestors upto and including /P/ but not
    the appenders in any of the ancestors of /P/.

    Loggers have their additivity flag set to |true| by default.


There is a table detailling the rules on the page.


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

View raw message