Wow! We had seen that truncation error too, but I thought it was the mad ramblings of an over tired developer so hadn't mentioned it...
Thanks for the feedback. I've sent another mail about the development status of log4net - it seems to be dormant which isn't really a good sign for an open source proj... Pete > -----Original Message----- > From: Dave Hutz [mailto:[EMAIL PROTECTED] > Sent: 29 June 2004 18:06 > To: 'Log4NET User' > Subject: RE: Restarting app can cause logging to stop? > > > I don't think that the bug has been fixed in a public > version. We patched it here, and I submitted the patch to the > dev list, but it doesn't look like it was incorporated. I've > attached the message I sent to the dev list > > Dave > > -----Original Message----- > From: Peter McEvoy [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 29, 2004 12:27 PM > To: Log4NET User > Subject: RE: Restarting app can cause logging to stop? > > > Thanks for the feedback. Although when restarting a web app, > we just touch the web.config: it's pretty hard to judge when > the next hit will come in. > > BTW, what version are you using? Will upgrading fix anything > do you think? > > Pete > > > -----Original Message----- > > From: Dave Hutz [mailto:[EMAIL PROTECTED] > > Sent: 29 June 2004 17:21 > > To: 'Log4NET User' > > Subject: RE: Restarting app can cause logging to stop? > > > > > > Yes, this happens to us pretty regularly. We found that > > introducing a delay of a few seconds between the stop and the > > start during the restart pretty much eliminates the problem. > > > > There is a bug logged for it in SourceForge(#872040). The > > root cause of that person's problem (permissions) is a little > > different than ours (file locking), but the solution is the same. > > > > Dave > > > > -----Original Message----- > > From: Peter McEvoy [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 29, 2004 12:03 PM > > To: [email protected] > > Subject: Restarting app can cause logging to stop? > > > > > > Folks, > > We are using log4net extensively in our applications which > > consist of a lot of windows services and web services. > > However we have spotted sometimes (only somtimes mind) that > > when a service is stopped and restarted, logging to the > > RollingLogFileAppender will completely stop; messages will > > not be written to the logfile any more, although messages > > _will_ get written to an EventLogAppender > > > > This is proving hard to reproduce, so I agree that this is > > little more than anecdotal, but I am wondering if anyone has > > seen this type of behaviour? > > > > We are using log4net-1.1 > > > > Pete > > >
