logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-383) Log4Net.Error throws VerificationException - Operation could destabilize the runtime
Date Wed, 17 Jul 2013 04:12:48 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710665#comment-13710665
] 

Arun commented on LOG4NET-383:
------------------------------

Here is the stack trace from a Test Application:

[VerificationException: Operation could destabilize the runtime.]
   log4net.Core.LogImpl.Error(Object message) +17
   Log4NetTest.WebForm2.Page_Load(Object sender, EventArgs e) in f:\CodeSamples\PortalTest\Log4NetTest\Log4NetTest\WebForm2.aspx.cs:13
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs
e) +25
   System.Web.UI.Control.LoadRecursive() +116
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+2793

The line of code that throws this exception is :
catch(ex)
{
    _log.Error("Exception caught", ex);
}

Whereas the following line works:
catch(ex)
{
    _log.Debug("Error found", ex);

}
                
> Log4Net.Error throws VerificationException - Operation could destabilize the runtime
> ------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-383
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-383
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.10, 1.2.11
>         Environment: IIS 7.5 / Win 2008 R2
> .Net 4.0
> MVC3 and WCF applications
>            Reporter: Arun
>
> We are running into this issue when we log errors/fatal message using log4net. 
> > System.Security.VerificationException: Operation could destabilize the
> > runtime.    at log4net.Core.LogImpl.Fatal(Object message, Exception
> > exception)
> Strangely this happens only when we log as Error/Fatal, Info and Debug messages log perfectly
fine. Because of this exception, the real exceptions are getting masked and its making it
very hard for us to debug in deployed environments. 
> I have tried searching online but to no avail. Any help is appreciated.
> Environment details:
>     IIS 7.5 / Win 2008 R2
>     .Net 4.0
>     MVC3 and WCF applications
> Here is the logging configuration-
>  
>        <?xml version="1.0" encoding="utf-8" ?>
>         <configuration>
>           <configSections>
>             <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler,
  log4net"/>
>           </configSections>  
>           <log4net>
>           <appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
>             <file value="C:\Logs\ApplicationServices.log" />
>             <staticLogFileName value="true" />
>             <appendToFile value="true" />
>             <datePattern value="yyyyMMdd" />
>             <rollingStyle value="Date" />
>             <filter type="log4net.Filter.LevelRangeFilter">
>             <acceptOnMatch value="true" />
>             <levelMin value="DEBUG" />
>             <levelMax value="FATAL" />
>             </filter>
>             <layout type="log4net.Layout.PatternLayout">      
>               <conversionPattern value="${COMPUTERNAME} %date %-5level %class.%method
- %message%newline"/>
>             </layout>
>           </appender>
>           <root>
>             <level value="DEBUG"/>
>             <appender-ref ref="RollingLogFileAppender" />
>           </root>
>         </log4net>
>         </configuration>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message