[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4net-user
Subject:    Re: Re[2]: Logging of the errors in logging
From:       Ron Grabowski <rongrabowski () yahoo ! com>
Date:       2006-04-03 4:26:35
Message-ID: 20060403042635.55816.qmail () web32201 ! mail ! mud ! yahoo ! com
[Download RAW message or body]

Your application can process messages written to
System.Diagnostic.Trace by using code like this in your App.Config:

<system.diagnostics>
 <trace autoflush="true">
  <listeners>
   <add name="textWriterTraceListener" 
    type="System.Diagnostics.TextWriterTraceListener"
     initializeData="C:\\Company\\Application\\Logs\\log4net.txt" />
  </listeners>
 </trace>
</system.diagnostics>

You can also configure that in code.

--- unegov <unegov@skbkontur.ru> wrote:

> Ok. But nevertheless log4net propagates logging problems into
> Console.Error and into Trace. Can I expect that in the near or
> distant
> future log4net will allow me to override this behaviour?
> I think it would not contradict the ideology of log4net as a best
> effort logging system. It would just give me chance to change the way
> I monitor problems with logging.
> 
> Thanks.
> 
> Best regards,
> Stepan Unegov.
> 
> NC> Log4net is designed to be a best effort logging system, not a
> reliable
> NC> system. If there is a problem logging log4net will not propagate
> errors
> NC> into the calling application. 
> NC> While the current internal error handling is not flexible enough
> it is
> NC> unlikely that it will be changed to accommodate a completely
> reliable
> NC> logging scenario. 
> 
> NC> Regards,
> NC> Nicko
> 
> >> -----Original Message-----
> >> From: unegov [mailto:unegov@skbkontur.ru] 
> >> Sent: 30 March 2006 08:43
> >> To: log4net-user@logging.apache.org
> >> Subject: Logging of the errors in logging
> >> 
> >> Log4net is a great tool but I'm not fully satisfied how 
> >> log4net deals with errors in logging. In my project it is 
> >> necessary not to lose any logging messages if the logging is 
> >> on so I would prefer log4net threw exceptions rather than 
> >> wrote errors of logging into Console.Error and Trace as 
> >> information messages. I'm ready to catch such sort of 
> >> exceptions at the top level of my code. But I have no way to 
> >> override the behaviour of the LogLog class.
> >> 
> >> All I can do is to intercept Console.Error and rethrow 
> >> exceptions in the interception code but in this case I wont 
> >> always get complete exception messages and it doesnt look 
> >> beautiful at all.
> >> 
> >> Another way is to rebuild log4net but I will get a lot of 
> >> problems with other projects (nhibernate) which references 
> >> native assembly of the log4net. So the question: is it 
> >> possible to add to log4net different strategies of managing 
> >> errors in logging? Is there any other way to cope with the
> problem?
> >> 
> >> ErrorHandlers used in appenders don't cover all possible errors.
> I.e.
> >> if some error in configuring occures it is most likely that 
> >> no appender will be added to logger.
> >> 
> >> Thanks.
> >> 
> >> Best regards,
> >> Stepan Unegov.
> >> 
> >> 
> >> 
> 
> 

[prev in list] [next in list] [prev in thread] [next in thread]