[
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764192#comment-13764192
]
Chirayu Shishodiya commented on LOG4NET-383:
--------------------------------------------
We have a user who hit this too. Our application is MVC3 and runs in .NET 4.
This is the stack trace he sent me:
VerificationException- Operation could destabilize the runtime.
at log4net.Core.LogImpl.Error(Object message, Exception exception)
at RedGate.Deploy.Portal.Application.DmController.OnException(ExceptionContext
exceptionContext)
at
System.Web.Mvc.ControllerActionInvoker.InvokeExceptionFilters(ControllerContext
controllerContext, IList`1 filters, Exception exception)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext
controllerContext, String actionName)
at System.Web.Mvc.Controller.ExecuteCore()
at System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext)
at
System.Web.Mvc.MvcHandler.<>c__DisplayClass6.<>c__DisplayClassb.<BeginProcessRequest>b__5()
at
System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass1.<MakeVoidDelegate>b__0()
at
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)
Have you guys reproduced this? Any help I can offer to reproduce this?
> 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
