Question

It seems that Log4Net silently shuts down for reasons that are not obvious, and I’m at a loss how to troubleshoot it. My hunch is that a particular appender is failing on a specific log message and that seems to shut down the whole stack.

Is there a way to get Log4Net to throw an exeception (at least during our debug phase) rather than a slient shutting down of the service.

Answer 1

I think there’s a config value you can put in the appSettings section of your app.config/web.config to turn on internal debug statements in log4net:

<appSettings>     <add key='log4net.Internal.Debug' value='true'/> </appSettings> 

This will give you some insight into any errors that log4net might be swallowing.