The BufferingForwardingAppender only depends on the number of events in the buffer not the length of time the events have been in the queue. It would add considerable complexity to the buffer to expire events after a period of idle time.
Nicko > -----Original Message----- > From: Marco von Frieling [mailto:[EMAIL PROTECTED] > Sent: 12 April 2006 12:15 > To: Log4NET User > Cc: [email protected] > Subject: BufferingForwardingAppender, another question > > Hi. > > Yesterday I had the problem that an NHibernate operation took > 3202 ms and the complete callback about 6 seconds, which > obviously is too long. So I configured an extra logger for > the NHibernate namespace hierarchy with level INFO instead of > DEBUG an the same operation has finished after 76 ms. But > logging root with DEBUG and NHibernate only with info does > not work for us during development. So I thaught it would be > the best thing to use a BufferingForwardingAppender > forwarding to the FileAppender. > > Then my project leader asked me what happens when the buffer > configured to 200 messages contains only 100 messages when > the request ends and no other request comes in for a while. > When will these 100 messages be written into the log file, > only if the buffer is full? Or is there a way to flush the > buffer when the current thread or process is idle? > > Thanks, Marco > > -- > Marco von Frieling > In den Ackern 8 > D-27374 Wittorf > > eMail: [EMAIL PROTECTED] > > "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... > Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail > >
