logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Abernethy" <greg.aberne...@hatsoft.ca>
Subject RE: log4net logging level INFO or DEBUG causes the web application to end
Date Tue, 06 Dec 2005 19:47:04 GMT
I got the exception "Global Application Error: Exception of type
System.Web.HttpUnhandledException was thrown." from Global.asax
I initially thought that the application was restarting and made sure that
no anti-virus or file-backup software was accessing the Global file. I still
think that the application was being restarted but I am not sure how it
would be related to log4net.

-----Original Message-----
From: Matthew Brown [mailto:octavius@gmail.com] 
Sent: Tuesday, December 06, 2005 12:12 PM
To: Log4NET User
Subject: Re: log4net logging level INFO or DEBUG causes the web application
to end

Do you get any sort of exception logged anyway?

What does "the application ended" mean exactly with your problem? With
Asp.NET, usually that means that the application has restarted..

On 12/6/05, Greg Abernethy <greg.abernethy@hatsoft.ca> wrote:
> I have an asp.net web application that uses log4net. I recently upgraded
> from 1.2.0 to 1.2.9 because I needed to use FileAppender+MinimalLock in
> order to access the log files while the application was running. I also
> some other changes to the application and started to get some strange
> behavior. The application would suddenly end for no apparent reason and at
> intermitted intervals. I added more logging to try to find out why this
> happening and changed the log level from INFO to DEBUG. After trying many
> things, I changed the log level to ERROR and no more application errors.
> After some more testing I found that with the log level set to INFO or
> the application would end suddenly, but raising the log level to WARN or
> ERROR stopped this behavior. The web application uses NHibernate O/R
> mapping, Forms Authentication and stores some objects in the session.
> Has anyone else had similar problems or a possible explanation? Is it
> possibly related to the amount of resources (memory) that log4net is
> One more thing - on my computer and on our demo server I could not
> these errors. The application only behaves this way on the production
> party) server. Here is the logging part of my web config:
>                 <appender name="FileLog"
> type="log4net.Appender.RollingFileAppender,log4net">
>                         <lockingModel
> type="log4net.Appender.FileAppender+MinimalLock" />
>                         <param name="File"
> />
>                         <param name="AppendToFile" value="true" />
>                         <param name="RollingStyle" value="Size" />
>                         <maxSizeRollBackups value="5" />
>                         <maximumFileSize value="100KB" />
>                         <param name="StaticLogFileName" value="true" />
>                         <layout type="log4net.Layout.PatternLayout">
>                                 <param name="ConversionPattern" value="%d
> %-5p %c - %m%n" />
>                         </layout>
>                 </appender>
>                 <root>
>                         <level value="DEBUG" />
>                         <appender-ref ref="FileLog" />
>                 </root>
>         <runtime>
>       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
>          <dependentAssembly>
>             <assemblyIdentity name="log4net"
>                               publicKeyToken="b32731d11ce58905"
>                               culture="neutral" />
>            <bindingRedirect oldVersion=""
>                         newVersion=""/>
>          </dependentAssembly>
>       </assemblyBinding>
>    </runtime>

View raw message