Database Appender
"Ismay, Greg (CALBRIS)" <[email protected]> Mon, 10 Jan 2005 14:00:51 +1000
| Newsgroups | gmane.comp.windows.dotnet.log4net.user |
|---|---|
| Message-ID | <218A413857CD974689C67A2ED680A0FE0D04C1@calbrsv025.cal.riotinto.org> |
howdy everyone... im using the database ADONetAppender to log to a sql server database and = its all going peachy keen... for a while... ive got the same app installed at 4 of our sites, with the appender = pointing back to a central database accessible over the wan (i will = probably end up using a local db at each site, but a central db was my = going in position, with a "lets see how it goes before we decentralise" = mentality). the wans pretty fast and im only doing production logging = (ie only errors and fatals) this way. basically, it works for a few days and sometimes up to a week or so, = before the logging just stops. forcing the loggers to reinitialised (ie by "touch"ing the = log4net.config file) makes it all good again... my question is this... are there any known problems with the db appender = (or any appender) whereby a loss of connection (which can happen over = the wan) over time could result in the above state (eg... maybe running = out of connections in the pool due to them gradually getting "stuck") ill troll through the code in a few minutes, but just thought id ask = first. thanks, Greg Ismay Specialist - Database Support (Automation Improvement) Comalco Aluminium Limited Phone : +61 7 3867 1853 Fax : +61 7 3867 1855 Mobile : +61 4 1760 6429 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt