Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET User" <log4net-user@logging.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4A132BD3.1050209@aps-technology.com>
Date: Tue, 19 May 2009 14:59:47 -0700
From: Loren Keagle <Loren@aps-technology.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Log4NET User <log4net-user@logging.apache.org>
Subject: Re: Log not logging in custom filter
References: <23624032.post@talk.nabble.com>
In-Reply-To: <23624032.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

stefan.moser wrote:
> I'm writing a custom filter (inherits from FilterSkeleton) and I want to log
> errors inside the filter.  The problem is that any log events created inside
> the filter is not getting logged.  Is there a special restriction that log
> events cannot be created this far down inside the loggin pipeline?
>
> public override FilterDecision Decide(LoggingEvent loggingEvent)
> {
>     // Do the interesting stuff
>
>     // In some exceptional case, log an error
>     LogManager.GetLogger("TheLogger").Error("log message", exception);
> }
>
> Any reason why this code wouldn't work?
>   

Inside of the log4net framework, there is an internal logger called 
LogLog.  It's used throughout the appender framework, but I imagine 
there's no problem using it in a filter.

Just call:

LogLog.Error("log message");


~Loren