Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 77639 invoked from network); 8 Apr 2009 14:39:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Apr 2009 14:39:38 -0000 Received: (qmail 18793 invoked by uid 500); 8 Apr 2009 14:38:21 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 18349 invoked by uid 500); 8 Apr 2009 14:38:20 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 17102 invoked by uid 99); 8 Apr 2009 14:31:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Apr 2009 14:31:03 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Apr 2009 14:30:54 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LrYnR-0003Ax-CH for log4net-user@logging.apache.org; Wed, 08 Apr 2009 07:30:33 -0700 Message-ID: <22951693.post@talk.nabble.com> Date: Wed, 8 Apr 2009 07:30:33 -0700 (PDT) From: omatase To: log4net-user@logging.apache.org Subject: Re: Error destroying my productivity Please Help!: log4net:ERROR [] Attempted to append to closed appender named [] In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: Omatase@gmail.com References: <22939427.post@talk.nabble.com> <362633.74338.qm@web30504.mail.mud.yahoo.com> <36C0E3BF5460C543B9ED4767D854AFD2031F53@server01.AS.local> X-Virus-Checked: Checked by ClamAV on apache.org Ross Hinkley wrote: > > You can specify a threshold value in the appender. That would allow you > to > log messages from a given level and higher. For example, as a child to > the > appender node: > > > > would log Info messages, Warning messages, and so on. From there, you can > use Ron's suggestion for controlling what you want to see overall and to > manage multiple appenders. > > Omatase, if you need a more complete example, let me know. > > -Ross > > I would love an example if you wouldn't mind. It sounds like what you are suggesting might not work in my situation though. I want to make these appenders available for any logging level. Someone else might have an application that they would like to send DEBUG messages to the FileAppender even though my application may only send FATAL messages to the same appender. Ross Hinkley wrote: > > If I understand your question, Omatase, it sounds like you want to log one > log level per file, maybe? I'm not certain you can specify an upper > threshold to an appender. I've never used log4net in such a fashion. > Does > anyone know if you can set an upper limit on an appender? > Since this is a service to be used by all applications developed at our company it could potentially be used differently by each application. For my application (The Invoicing example) I want to be able to send FATAL messages to the FileAppender and DEBUG messages to the AdoNetAppender not separated by file. -- View this message in context: http://www.nabble.com/Error-destroying-my-productivity-Please-Help%21%3A-log4net%3AERROR----Attempted-to-append-to-closed-appender-named----tp22939427p22951693.html Sent from the Log4net - Users mailing list archive at Nabble.com.