Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 8242 invoked from network); 28 Sep 2005 15:38:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Sep 2005 15:38:11 -0000 Received: (qmail 80337 invoked by uid 500); 28 Sep 2005 15:38:10 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 80225 invoked by uid 500); 28 Sep 2005 15:38:08 -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 80212 invoked by uid 99); 28 Sep 2005 15:38:08 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2005 08:38:08 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [66.250.23.133] (HELO BACKOFFICE.meridian7.com) (66.250.23.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2005 08:38:12 -0700 Subject: RE: SmtpAppender buffer flush (to mail) on shutdown. Date: Wed, 28 Sep 2005 09:40:19 -0600 Message-ID: <3A7E4909010C6A4E8D9CF4E5428DDBD49F60BA@backoffice.meridian7.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SmtpAppender buffer flush (to mail) on shutdown. Content-class: urn:content-classes:message Thread-Index: AcW+VDfgQuiPhPVDQU6WuVI4V2EyiwCxhwBAAMYuzrAAA6J4wA== From: "Adam Jack" X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0 To: "Log4NET User" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I am using 1.2.9 (release from Apache Incubator.) Could it be that this is too 'old'?=20 If not, then I'll triple check that what I last saw didn't have lossy somehow set. Maybe it was a residual message from that configuration, since I've not noticed one recently. Sorry if this was all "lossy" related. Thanks for investigating. Regards, Adam -----Original Message----- From: Nicko Cadell [mailto:nicko@neoworks.com]=20 Sent: Wednesday, September 28, 2005 7:50 AM To: Log4NET User Subject: RE: SmtpAppender buffer flush (to mail) on shutdown. Adam, If the SmtpAppender is configured not to be lossy (i.e. Lossy=3Dfalse) then the current buffer will be sent. If the appender is in lossy mode (Lossy=3Dtrue) then the buffer is not sent when the appender is closed. As you are not seeing this behaviour, which version of log4net are you using? Cheers, Nicko > -----Original Message----- > From: Adam Jack [mailto:adam.jack@AdventureCentral.com]=20 > Sent: 24 September 2005 16:15 > To: log4net-user@logging.apache.org > Subject: RE: SmtpAppender buffer flush (to mail) on shutdown. >=20 > I've experienced this even with lossy=3D"true", so I don't=20 > believe this is the issues. Anybody have any insights into=20 > how I might stop this buffer flush to mail? >=20 > =20 >=20 > Regards, >=20 > =20 >=20 > Adam >=20 > ________________________________ >=20 > From: Adam Jack > Sent: Tuesday, September 20, 2005 8:29 PM > To: 'log4net-user@logging.apache.org' > Subject: SmtpAppender buffer flush (to mail) on shutdown. >=20 > =20 >=20 > Howdy folks, >=20 > =20 >=20 > I hope this isn't an FAQ, but I couldn't find the answer in=20 > mailing list archives or in the documentation.=20 >=20 > =20 >=20 > I have an SmtpAppender pretty much configured as in the example: >=20 > =20 >=20 > =20 > http://logging.apache.org/log4net/release/config-examples.html > #smtpappender >=20 > =20 >=20 > It is running inside my webapp (configured in the web.config)=20 > and works wonderfully, e-mailing me when I get a page=20 > crash/error event.=20 >=20 > =20 >=20 > The only bummer is sometimes it e-mails me when nothing is=20 > wrong, but the webapp has timed out (and is being torn down.)=20 > The buffer of non-error log message is sent to me. I've=20 > attached the config below, and looking at it I see lossy set=20 > to false - which is a worry, I'll set it true again - but I'm=20 > pretty certain I only tinkered with that setting when this=20 > started happening. Of course, I was preparing this e-mail as=20 > I found that setting.=20 >=20 > =20 >=20 > Time will tell if this fixes the problem, but I'd really=20 > appreciate insights. Is this a designed in feature, or an=20 > unintentional side effect? If intentional can I disable it=20 > with some (say) disable statement when I capture the shutdown event? >=20 > =20 >=20 > Thanks for insights, and thanks for this product on this platform. >=20 > =20 >=20 > Regards >=20 > =20 >=20 > Adam >=20 > -- >=20 > Adventure Central >=20 > http://www.AdventureCentral.com >=20 > "Great Experiences Deserve Great Technology" >=20 > 303 292 5522 x111 >=20 > Denver, CO USA >=20 > =20 >=20 > =20 >=20 > =20 >=20 > type=3D"log4net.Appender.SmtpAppender,log4net"> >=20 > value=3D"Adam.Jack@AdventureCentral.com" /> >=20 > value=3D"dev@AdventureCentral.com" /> >=20 > value=3D"AdventureWeb Logging." /> >=20 > >=20 > >=20 > type=3D"log4net.Core.LevelEvaluator,log4net"> >=20 > value=3D"ERROR" /> >=20 > >=20 > type=3D"log4net.Layout.PatternLayout,log4net"> >=20 > =20 > %level :: %message %newlineLogger: %logger%newlineThread:=20 > %thread%newlineDate: %date%newlineNDC:=20 > %property{NDC}%newline%newline" /> >=20 > >=20 > =20 >=20 >=20