override protected void = SendBuffer(LoggingEvent[]=20 events)

{

if (m_reconnectOnError && = (m_dbConnection =3D=3D null ||

=20 =20 m_dbConnection.State !=3D=20 ConnectionState.Open))

{

=20 LogLog.Debug("AdoNetAppender: Attempting to reconnect to=20 database.

=20 &= nbsp; Current = Connection State: " = +

=20 ((m_dbConnection=3D=3Dnull)?"<null>":m_dbConnection.State.ToString(= ))=20 );

=20 InitializeDatabaseConnection();

=20 InitializeDatabaseCommand();

}

Thanks = &=20 regards,

Raghu

-----Original Message-----
From: Georg Jansen=20 [mailto:Georg.Jansen@FaktNet.com]
Sent: Friday, February 03, = 2006=20 11:07 AM
To: 'Log4NET User'
Subject: RE: Database=20 Appender

Raghu,

You set the = parameter=20 in the AdoNetAppender, like:

<appender=20 name=3D"AdoNetAppender" type=3D"log4net.Appender.AdoNetAppender">      =20

  =20 <reconnectonerror=20 value=3D"true" = />

  =20 +++ other AdoNetAppender parameters

     =20

But like = I=20 mentioned in my previous post, I couldn’t see that it had any = impact (at least=20 not from the tests I did), that’s way I wrote the new version of = the=20 SendBuffer method.

Regards

Georg

http://www.l4ndash.com = Log4Net Dashboard=20 / Log4Net Viewer

From:=20 Bejugam, Raghavendra (GE Commercial Finance, NonGE)=20 [mailto:raghavendra.bejugam@ge.com]
Sent: 3. februar 2006 = 15:51
To: Log4NET=20 User
Subject: RE: Database=20 Appender

Any idea = where to set=20 this property

ReconnectOnError to=20 TRUE. If some one can provide me the sample syntax of config file it = would=20 help.

Thanks,

Raghu

-----Original=20 Message-----
From: Georg Jansen=20 [mailto:Georg.Jansen@FaktNet.com]
Sent: Thursday, February 02, = 2006 11:22=20 AM
To: = 'Log4NET User'
Subject: RE: Database=20 Appender

Simon,

I believe it was = done some=20 work on that in 1.2.9 (you are using an earlier version,=20 right?)

I checked the source = code for=20 the AdoNetAppender, and in the SendBuffer it tries to do a reconnect = (if the=20 parameter reconnectonerror is stated in the=20 config).

override protected void = SendBuffer(LoggingEvent[]=20 events)

{

   if (m_reconnectOnError = &&=20 (m_dbConnection =3D=3D null ||

     =20            =20 m_dbConnection.State !=3D=20 ConnectionState.Open))

   = {

     =20 LogLog.Debug("AdoNetAppender: Attempting to reconnect to=20 database.

  =20 =             &= nbsp;  Current = Connection State: "=20 +

     =20 = ((m_dbConnection=3D=3Dnull)?"<null>":m_dbConnection.State.ToString(= ))=20 );

     =20 InitializeDatabaseConnection();

     =20 InitializeDatabaseCommand();

   = }

Problem is that when = I tested=20 this (I restarted SQL server between two log statements), I still = gets an=20 exception stating a “transport layer = error”.

I agree with you, = Simon this=20 is a problem with applications running for a long time for example = web=20 applications. A simple solution would be to modify the = adonetappender and=20 try to do a reconnect whenever the sql statement fails (I will give = it a=20 try).

Regards

Georg

http://www.l4ndash.com Log4Net = Dashboard /=20 Log4Net Viewer

-----Original Message-----
From: Simon Wallis=20 [mailto:mailing@wallis.ca]
Sent: 2. februar 2006 16:31
To:=20 Log4NET = User
Subject: RE:=20 Database Appender

Hi,

Has anyone come up with any creative ways = to solve=20 this problem of the database connection hanging? The only thing I = can think=20 of is to have a process = that=20 "touches" the config file on an hourly basis. Otherwise we have to = remember=20 to go around doing this manually on all the servers whenever the = database is=20 rebooted or there's a temporary network=20 failure.

I realize it would be a lot of work to add = retry or=20 failure semantics to the appender, but whenever this is implemented, = likely=20 the most flexible approach would be to provide a number of options = via the=20 config file.

Simon.

-----Original Message-----

Subject:    RE: = Database=20 Appender

From:       = "Nicko=20 Cadell" <nicko () neoworks ! com>

Date:       = 2005-01-10=20 13:59:27

Message-ID: = DDEB64C8619AC64DBC074208B046611C59C838=20 () kronos ! neoworks ! co ! uk<= /P>
[Download message RAW]

Greg,

The AdoNetAppender does not reopen the = connection if=20 there is a failure.

The database connection is only opened = during=20 appender initialisation.

Error handling is a general = issue for appenders but for=20 the

AdoNetAppender there are a number of = options.=20

The current behaviour is for the appender = to stop=20 trying to write to the

database if the connection is closed. An = alternative=20 is for the appender

to try to reconnect to the database. The=20 issues with = reconnecting=20 is

when to try and how many times. The = appender could=20 try to reconnect when

the buffered events are sent. If it fails = to contact=20 the server then the

connection will time out after some time. = This is a=20 synchronous call and

therefore any logging call in your = application could=20 randomly incur this

connection timeout penalty at any time. Is = that=20 acceptable behaviour for

the appender? If the appender cannot = reconnect=20 should it discard the

events that it cannot deliver? or should = it store=20 the events and

redeliver them when/if it does reconnect, = if so how=20 many event should it

store?

There are no easy solutions to these=20 issues, and different=20 behaviours

will be appropriate for different = situations. The=20 current AdoNetAppender

implementation does not attempt to support = any retry=20 or failure

semantics. This is one area where we will = need to do=20 some work in

future. If you have any suggestions we = would be=20 happy to discuss them.=20

Nicko

> -----Original Message-----

> From: Ismay, Greg (CALBRIS)=20

> = [mailto:Greg.Ismay@comalco.riotinto.com.au]=20

> Sent: 10 January 2005=20 04:15

> To:=20 log4net-user@logging.apache.org

> Subject: Database=20 Appender

>

>

> > howdy=20 everyone...

> >

> > im using the database = ADONetAppender to=20 log to a sql server

> database and its all going peachy = keen... for a=20 while...

> >

> > ive got the same app installed = at 4 of our=20 sites, with the

> appender pointing back to a central = database=20 accessible over=20

> the wan (i will probably end up using = a local=20 db at each

> site, but a central db was my going = in=20 position, with a "lets

> see how it goes before we = decentralise"=20 mentality). the wans

> pretty fast and im only doing = production=20 logging (ie only

> errors and fatals) this=20 way.

> >

> > basically, it works for a few = days and=20 sometimes up to a

> week or so, before the logging just=20 stops.

> >

> > forcing the loggers to = reinitialised (ie=20 by "touch"ing the

> log4net.config file) makes it all = good=20 again...

> >

> > my question is this... are there = any known=20 problems with the db

> > appender (or any appender) = whereby a=20 loss of connection = (which can=20

> > happen over the wan) over time = could=20 result in the above

> state (eg... =

> > maybe running out of connections = in the=20 pool due to them gradually

> > getting=20 "stuck")

> >

> > ill troll through the code in a = few=20 minutes, but just

> thought id ask=20 first.

> >

> > = thanks,

> >

> > Greg = Ismay

> >

> > Specialist - Database Support = (Automation=20 Improvement) Comalco

> > Aluminium=20 Limited

> >

> > Phone :   +61 7 = 3867=20 1853

> > Fax    = :   +61 7=20 3867 1855

> > Mobile :   +61 4 = 1760=20 6429

> >

>=20

------_=_NextPart_001_01C628DC.9194A090--