catching log4net exceptions

Question

I need to catch log4net exceptions (its own exceptions not app exceptions logged by it). I wish there's a way of doing it this way:

Try
    _logger.Info(response)
Catch ex As Exception
    Excepciones.HandleException(ex, "PolicyCore")
End Try

I have this code implemented and there's no errors in compilation but i force log4net to have an error (pointing to a non existing database in the config file) and nothing is threw.
I've tried the listener aproach:

 <appSettings>
        <add key="log4net.Internal.Debug" value="true" />
    </appSettings>
    <system.diagnostics>
       <trace autoflush="true" indentsize="4" >
         <listeners>
           <add name="textWriterTraceListener" 
               type="System.Diagnostics.TextWriterTraceListener"
               initializeData="C:\\temp\\log4net.txt" />
           <remove name="Default" />
         </listeners>
       </trace>
    </system.diagnostics>

and it's writing the errors to log4net.txt, the forced ones i mean.

This last aproach has a couple of drawbacks: it won't append every error to the file, if the error is the same it doesn't write it, i can't get the listener to write every error to that file, only one (I don't know how to fully configure the trace listener, it might be that). Thus it won't append the date and hour to every line wich is a necesity for me. Finally i can't give structure to it (xml).

Even if the listener work i need to use the try/catch aproach, since i'm using ExceptionHandling from Enterprise library to log the errors in my app.

Anyone who has faced the problem and/or has a solution?

score 2 · Accepted Answer · edited May 23 '17 at 12:31

2

Log4net is designed not to throw any exceptions. This seems to be a good idea because it would be very bad indeed if your application fails because it cannot log. So if you need to log certain messages and need to be sure that this worked, then you should not use a log framework, but rather implement this as part of your "business logic".

You mention that an exception is logged only once. I think that is not true: Log4net usually disables appenders that do not work and thus there is only one exception. The AdoNetAppender for instance can be configured to re-connect to the database in case of a failure in which case you would see the same exception multiple times.

edited May 23 '17 at 12:31

Community

1
1

answered Jan 24 '12 at 13:47

Stefan Egli

17,398
3
54
75

i didn't know log4net disabled appenders that don't work. That was the reason why i couldn't see more than one error for that appender. i was trying this aproach because the app we're implementing may serve as a legal key and therefore it'll need to log everything including log4net errors in case the app fails. It seems very complicated to save the errors from the trace to enterprise library exception handling. I'm going to use it as it is: a logging framework. BL will handle all the necesary logic. Thank you very much. – euther Jan 24 '12 at 18:59
3

@Stefan "Log4net is designed not to throw any exceptions" then if the logging fails how we can find the reason why it fails? – VJAI Apr 11 '12 at 13:40
You can turn on "internal debugging". you find information about this in the log4net faq: http://logging.apache.org/log4net/release/faq.html – Stefan Egli Apr 11 '12 at 14:16

catching log4net exceptions

1 Answers1