The FAQ states that log4net is not a reliable logging system:

 http://logging.apache.org/log4net/release/faq.html

If you want something that is truly reliable my guess is that you'd have to 
check the target to make sure information was received correctly. Maybe the 
EventLog, syslog, or a message queue guarantee reliability. What happens when 
the EventLog reaches its maximum size? 

In the case of a FileAppender you might be able to turn on flushing after every 
write then check to the length of the file (or open the file and seek to the 
end) to make sure data has been written. CountingQuietTextWriter keeps track of 
the number of bytes written to a file.

Verifying every message is written will definitely slow things down.

----- Original Message ----
From: Knittel Bruno <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, January 7, 2008 6:11:18 AM
Subject: Error handling: how to be sure logs were correctly written ?





 
 


<!--

 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times 
New Roman";}
a:link, span.MsoHyperlink
        {color:blue;text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;text-decoration:underline;}
span.emailformatvorlage17
        {font-family:Arial;color:windowtext;}
span.emailformatvorlage18
        {font-family:Arial;color:navy;}
span.EmailFormatvorlage19
        {font-family:Arial;color:navy;}
 _filtered {margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
        {}
-->






Hello everyone,


 


           
We need a logging framework that runs on CF 2.0 (as log4net
exists for CF 1.0, it runs on CF 2.0) that can assure us that log was
successfully performed on every Appender.


 


           
In fact we want our application to be told by the logging framework if log was
successful. 


 


Is this possible with the
log4net framework?


If yes, what about the
TCP/IP network appenders?


 


Thanks in advance for
your help,


 


Bruno Knittel 


 








Reply via email to