hi,
appenders are inherited from parent-loggers, so your logger
"MyNamespace.MyClass" infact has 2 appenders: "smtpAppender" AND
"rollingFileAppender". to avoid this, set the "additivity" attribute on
your logger to "false"
<logger name="MyNamespace.MyClass" additivity="false">
<level value="INFO" />
<appender-ref ref="rollingFileAppender" />
</logger>
hth
franz
________________________________
Von: Mike Raath [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 21. Dezember 2005 10:04
An: [email protected]
Betreff: BUG? Parent appenders log based on child appender level
I've got a requirement where I need one appender to log info level
messages to a log file, which I've defined as a RollingFileAppender, and
error messages to a mail, which is an appender I've written myself
called HtmlSmtpAppender (see my earlier post regarding html format
mails).
The config entry looks like this:
<log4net>
<appender name="smtpAppender"
type="log4net.Appender.HtmlSmtpAppender">
<to value=" [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> " />
<from value="[EMAIL PROTECTED]" />
<subject value="Application Error" />
<smtpHost value="somesmtpserver.com" />
</appender>
<appender name="rollingFileAppender"
type="log4net.Appender.RollingFileAppender " >
<file value="Application.log" />
<RollingStyle value="Date" />
<datePattern value="yyyyMMdd" />
<layout type=" log4net.Layout.PatternLayout">
<conversionPattern value="%newline%date %-4timestamp
[%thread] %-5level %logger %ndc - %message%newline" />
</layout>
</appender>
<!-- Set root logger level to DEBUG and its only appender to A1
-->
<root>
<level value="ERROR" />
<appender-ref ref="smtpAppender" />
</root>
<logger name="MyNamespace.MyClass">
<level value="INFO" />
<appender-ref ref="rollingFileAppender" />
</logger>
</log4net>
Now what I've noticed is that when an INFO event is logged, the
MyNameSpace.MyClass Logger is tested against the defined log level and
correctly called. However, when the appender hierarchy is iterated, and
we get to the root logger, its append is called even though it has a
level set to error.
Is this an error in my understanding of how the hierarchy is used, or is
it a bug? I wanted a catch-all error logger but obviously I can achieve
what I want as things currently stand by defining a root debug logger
and a class (or parent namespce) logger which logs error events.
Regards,
Mike