The log4net.txt file was meant to help you track down problems after
the application has been running for a while. If you let you
application run for a few days or weeks and the RollingFileAppender
fails, there's a good chance the log4net.txt file will tell you what's
going wrong.
--- Fahad Sarwar
e caused by the RollingFileAppender? If things have been
fixed for next release then maybe switching to log4net 1.2.9 maybe better.
Fahad
-Original Message-
From: Ron Grabowski [mailto:[EMAIL PROTECTED]
Sent: 12 December 2005 22:28
To: Log4NET User
Subject: RE: RollingFileAppender Stops logging in W
he beginning of the Main()
> method
> etc.
>
> Btw I havent referenced log4net.LogManager.Shutdown(); in any of my
> code.
>
> thanks
> Fahad
>
> -Original Message-
> From: Ron Grabowski [mailto:[EMAIL PROTECTED]
> Sent: 12 December 2005 16:11
> To
Stops logging in Web Service
Perhaps there is something wrong in your
Opal.Logging.LogEntry.SetConfigurator method. Can we see the source to that?
My Application_End usually includes a simple message to help my keep track
of when the app domain gets unloaded.
protected void Application_End(Object
Perhaps there is something wrong in your
Opal.Logging.LogEntry.SetConfigurator method. Can we see the source to
that? My Application_End usually includes a simple message to help my
keep track of when the app domain gets unloaded.
protected void Application_End(Object sender, EventArgs e)
{
lo
Hi, I am using
Log4Net within a WebService. I have been successfully logging to a file
using the RollingFileAppender, however recently the webservice stops logging
completly to the file for no apparant reason. The WebService continues to
work successfully but no logs are generated. I have