Rather than try to ask specific troubleshooting questions, I have a broad internal question. Is there any known way that the ADONetAppender would not log to the database yet not throw an exception? Will version 1.2.9 behave any better in this area?
Sorry to be such a PITA. Log4net works just fine for developers, but doesn't seem to like the database from the production environement. The IT people assure us that the prod. env. is identical to the staging env. ;)
Kevin Williams wrote:
Nicko Cadell wrote:
Kevin,
Setting the BufferSize to any value less than or equal to 1 should have the same effect; to log synchronously.
It didn't seem to be that way. It was 0 when it was logging sometimes at best. Once we set it to 1, it seemed to log responsively as would be expected. That may not be the correct behavior, but it is what we observed.
Previously you said "but the database is flaky at best. Sometimes it will work, sometimes it just won't log anything" later you seem to indicate that *nothing* at all is logged to the database. What are the symptoms you are seeing?
If the appender is failing then any errors will be logged via internal debug:
http://logging.apache.org/log4net/release/faq.html#internalDebug
It is typically best to use the appSettings to enable internal debug:
<appSettings> <add key="log4net.Internal.Debug" value="true"/>
You will need to use dbgview from http://www.sysinternals.com to view the debug.
I may still try that. I forgot it only logged debug info to the system debug mode and console output only. Doh!
If the database appender works for a bit, but then dies completely then it may be loosing its database connection. There is a ReconnectOnError property on the AdoNetAppender in log4net 1.2.9. Setting this to true will cause the appender to try to reconnect if the connection is lost.
Yes, I'm anxiously awaiting the final release of 1.2.9.
Nicko
Thanks for the help!
Kevin
---------- Scanned for viruses by ClamAV
---------- Scanned for viruses by ClamAV
