You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Dominik Psenner (JIRA)" <ji...@apache.org> on 2013/06/05 11:40:20 UTC

[jira] [Updated] (LOG4NET-330) Service fails to start if MailAppender threshold value is INFO or lower.

     [ https://issues.apache.org/jira/browse/LOG4NET-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Psenner updated LOG4NET-330:
------------------------------------

    Priority: Minor  (was: Major)

Given that this issue is not reproducable for us and there was no activity for an entire year, I'm decreasing the priority to minor.
                
> Service fails to start if MailAppender threshold value is INFO or lower.  
> --------------------------------------------------------------------------
>
>                 Key: LOG4NET-330
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-330
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.11
>         Environment: Windows 2008 R2 x64.  
>            Reporter: Bruce Cummins
>            Priority: Minor
>
> If I place the following mail appender in our service config file, and add an appender reference, the service will not start.  If I set the threshold to WARN or higher, the service starts.  
> Worked fine in previous versions of log4net.
> <appender name="MailAppender" type="log4net.Appender.SmtpAppender">
> 		<threshold value="INFO" />
> 		<to value="mail@mail.com" />
> 		<from value="mail@mail.com"/>
> 		<subject type="log4net.Util.PatternString" value="%date{yyyy MM dd}: %appdomain at %env{COMPUTERNAME} threw an error" />
> 		<smtpHost value="MailHost"/>
> 		<port value="25" />
> 		<authentication value="None" />
> 		<layout type="log4net.Layout.PatternLayout">
> 			<conversionPattern value="%date [%thread] %-5level %logger - %message%newline" />
> 		</layout>
> 		<bufferSize value="10"/>		
> 	</appender>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira