Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 20378 invoked from network); 30 Jul 2010 01:13:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Jul 2010 01:13:42 -0000 Received: (qmail 88353 invoked by uid 500); 30 Jul 2010 01:13:42 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 88275 invoked by uid 500); 30 Jul 2010 01:13:41 -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 88267 invoked by uid 99); 30 Jul 2010 01:13:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jul 2010 01:13:41 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shally.chong@gmail.com designates 209.85.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vw0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jul 2010 01:13:34 +0000 Received: by vws13 with SMTP id 13so1105048vws.34 for ; Thu, 29 Jul 2010 18:13:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=4x4YojqKU+8BnFg76lsyaWQoN7+OiyoUaM9vK6IGQiY=; b=WOtBmUrfsnxUzPBLbvMpPSamr5zux2s/Dc7rQcjYLPOLh5+TDSsDJna7oxNNIBp3+t kW3ULbvxY7I45IIMwqHk4SyLtLnSPl6QJfWhwbC4r4kSDfC0RgGOx542MTjVQBs/LGPP C1NSdV/XEXr63CdR86yno0TxlOdReAF3bHfOg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YZVZP48R4maV8mZ26XidD+gNHgOPbXIE/uXxRPQG3RkHKXWAw2s/AyyTNbrhgGsFzE TsEm1cEPVJGorzMSYhnpJPjiCl4HRyljMAz6RRFJ6u7XBMnlULFOBKQoOz4P0DdyI8yd eNxzwQIPCp+gh1fUrcNjcMKdXDA32nG48Z1f8= MIME-Version: 1.0 Received: by 10.220.89.68 with SMTP id d4mr569814vcm.238.1280452392954; Thu, 29 Jul 2010 18:13:12 -0700 (PDT) Received: by 10.220.200.199 with HTTP; Thu, 29 Jul 2010 18:13:12 -0700 (PDT) In-Reply-To: <002901cb2f17$1ab69e00$5023da00$@org> References: <000601cb2ecb$03cc4ab0$0b64e010$@org> <002901cb2f17$1ab69e00$5023da00$@org> Date: Fri, 30 Jul 2010 09:13:12 +0800 Message-ID: Subject: Re: ADONetAppender not logging From: shally chong To: Log4NET User Content-Type: multipart/alternative; boundary=0016364ed26808aba6048c908ed7 X-Virus-Checked: Checked by ClamAV on apache.org --0016364ed26808aba6048c908ed7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Rob, I notice that and I've included it in my configuration files. I'm able to trap the mysql connection error with the internal logging file. Exception: "an established connection was aborted by the software in your host machine" was thrown. Regards, Shally On Thu, Jul 29, 2010 at 8:10 PM, Rob Prouse wrote: > Shally, > > > > Looking at the code for AdoNetAppender, it will not log if the connection > is lost and the reconnect fails. It will however output problems to its > internal logging. I think your best option right now is to enable log4net= =92s > internal logging and see if it can help diagnose the problem. > > > > See the section entitled =93How do I enable log4net internal debugging?= =94 near > the bottom of the FAQ. > > > > http://logging.apache.org/log4net/release/faq.html > > > > Rob Prouse > > > > *From:* shally chong [mailto:shally.chong@gmail.com] > *Sent:* Wednesday, July 28, 2010 11:44 PM > > *To:* Log4NET User > *Subject:* Re: ADONetAppender not logging > > > > Hi Rob, > > Yes, this happened after server rebooted. > There is no windows update or other software updates, where DC only > performing san storage (which requires server reboot). > Server guy has checked on the server side and did not find any different = on > the server after rebooted. > Previously I suspect the symantec/ live update caused the appender not > working. But later on, the symantec and all it's related component is > disabled, and still the appender not able to capture log after data loadi= ng > process resume. > > Regards, > Shally > > On Thu, Jul 29, 2010 at 11:06 AM, Rob Prouse wrote: > > Shally, > > > > You say that this started happening after the server rebooted, correct? > > > > Why was the server rebooted? Were there any Windows updates or other > software updates that required the reboot? Since it was working before th= e > reboot, we need to figure out what changed on the server to cause the > failure. There may be a bug in the AdoNetAppender, but whatever changed o= n > the server probably caused the bug to appear, so knowing what changed wil= l > help us track down the problem. > > > > My first thoughts are an update to the .NET runtime, or to the MySQL > server. > > > > Rob Prouse > > > > *From:* shally chong [mailto:shally.chong@gmail.com] > *Sent:* Wednesday, July 28, 2010 9:29 PM > *To:* Log4NET User > *Subject:* Re: ADONetAppender not logging > > > > Hi Rob, > > Yes, I included the ReconnectOnError clause in my configuration and the l= og > is obtained. > Any idea why the connection issue happened after the server reboot? > > All these while, I did not face such problem. > > Thanks, > Shally > > On Wed, Jul 28, 2010 at 9:29 PM, Rob Prouse wrote: > > Shally, > > > > In your configuration for the AdoNetAppender, do you have ReconnectOnErro= r > set to true? It defaults to false and is not in the example configuration= . > > > > > http://logging.apache.org/log4net/release/sdk/log4net.Appender.AdoNetAppe= nder.ReconnectOnError.html > > > > If not, add the following line to the appender and see if it helps. > > > > > > > > Hope this works for you, > > > > Rob Prouse > > > > *From:* shally chong [mailto:shally.chong@gmail.com] > *Sent:* Wednesday, July 28, 2010 1:52 AM > > > *To:* log4net-user@logging.apache.org > > *Subject:* Fwd: ADONetAppender not logging > > > > > > Hi, > > I encountered a problem with ADONetAppender in production server after th= e > DC perform restart for that server. > I have a .net c# window application where it will do some data loading in= to > mysql server. After the data loading completed or any exception thrown > during the data loading process, log4net will capture the error and store > into mysql table as well. There will be no file loading from 2am - 6am, > where during this time, there will be no log captured into mysql. Initial= ly, > after the file loaded into server at 6am, the log4net will start capturin= g > log again. All these while, the log4net is able to capture log after the > data loading process resume. But after the server being restarted, there = is > no more log captured into mysql after data loading process resume. And I > have to manually restart the window services (the window application runn= ing > as window services) daily to obtain the log again. > I've tried to modify the log4net to capture log into flat file, and it's > working fine (all logs are captured after data loading process resume). > > Please take note that the data loading process is working fine and data a= re > inserted into mysql server correctly. The only not working is ADONetAppen= der > is not capturing any logs after data loading process resume. > > Please advise. > > Thanks, > Shally > > > --0016364ed26808aba6048c908ed7 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Rob,

I notice that and I've included it in my configuration f= iles.
I'm able to trap the mysql connection error with the internal = logging file.
Exception: "an established connection was aborted by = the software in your host machine" was thrown.

Regards,
Shally

On Thu, Jul 29, 20= 10 at 8:10 PM, Rob Prouse <rob@prouse.org> wrote:

Shally,

=A0

Looking at the code fo= r AdoNetAppender, it will not log if the connection is lost and the reconnect fails. It will however output problems to its internal logging. I think you= r best option right now is to enable log4net=92s internal logging and see if it can help diagnose the problem.

=A0

See the section entitl= ed =93How do I enable log4net internal debugging?=94 near the bottom of the FAQ.

=A0

http://logging.a= pache.org/log4net/release/faq.html

=A0

Rob Prouse

=A0

F= rom: shally chon= g [mailto:shally.= chong@gmail.com]
Sent: Wednesday, July 28, 2010 11:44 PM


To: Log4NET User
Subject: Re: ADONetAppender not logging

=A0

Hi Rob,

Yes, this happened after server rebooted.
There is no windows update or other software updates, where DC only perform= ing san storage (which requires server reboot).
Server guy has checked on the server side and did not find any different on= the server after rebooted.
Previously I suspect the symantec/ live update caused the appender not work= ing. But later on, the symantec and all it's related component is disabled, = and still the appender not able to capture log after data loading process resum= e.

Regards,
Shally

On Thu, Jul 29, 2010 at 11:06 AM, Rob Prouse <rob@prouse.org> wro= te:

Shally,

=A0

You say that this star= ted happening after the server rebooted, correct?

=A0

Why was the server reb= ooted? Were there any Windows updates or other software updates that required the reboot? Since it was working be= fore the reboot, we need to figure out what changed on the server to cause the failure. There may be a bug in the AdoNetAppender, but whatever changed on = the server probably caused the bug to appear, so knowing what changed will help= us track down the problem.

=A0

My first thoughts are = an update to the .NET runtime, or to the MySQL server.

=A0

Rob Prouse

=A0

F= rom: shally chon= g [mailto:shall= y.chong@gmail.com]
Sent: Wednesday, July 28, 2010 9:29 PM
To: Log4NET User
Subject: Re: ADONetAppender not logging

=A0

Hi Rob,

Yes, I included the ReconnectOnError clause in my configuration and the log= is obtained.
Any idea why the connection issue happened after the server reboot?

All these while, I did not face such problem.

Thanks,
Shally

On Wed, Jul 28, 2010 at 9:29 PM, Rob Prouse <Rob.Prouse@ivara.com> wrote:

Shally,

=A0

In your configuration for the AdoNetAppender, do you have ReconnectOnError set to true? It defaults to fa= lse and is not in the example configuration.

=A0

http://logging.apache.org/log4net/release/sdk/log4net.Appender.AdoNetAppen= der.ReconnectOnError.html

=A0

If not, add the following line to the appender and see if it helps.

=A0

<reconnectOnError value=3D=94true=94>

=A0

Hope this works for you,

=A0

Rob Prouse

=A0

F= rom: shally chon= g [mailto:shall= y.chong@gmail.com]
Sent: Wednesday, July 28, 2010 1:52 AM

S= ubject: Fwd: ADO= NetAppender not logging

=A0

=A0

Hi,

I encountered a problem with ADONetAppender in production server after the = DC perform restart for that server.
I have a .net c# window application where it will do some data loading into mysql server. After the data loading completed or any exception thrown duri= ng the data loading process, log4net will capture the error and store into mys= ql table as well. There will be no file loading from 2am - 6am, where during t= his time, there will be no log captured into mysql. Initially, after the file loaded into server at 6am, the log4net will start capturing log again. All these while, the log4net is able to capture log after the data loading proc= ess resume. But after the server being restarted, there is no more log captured= into mysql after data loading process resume. And I have to manually restart the window services (the window application running as window services) daily t= o obtain the log again.
I've tried to modify the log4net to capture log into flat file, and it&= #39;s working fine (all logs are captured after data loading process resume).

Please take note that the data loading process is working fine and data are inserted into mysql server correctly. The only not working is ADONetAppende= r is not capturing any logs after data loading process resume.

Please advise.

Thanks,
Shally

=A0

--0016364ed26808aba6048c908ed7--