You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Kira Resari (JIRA)" <ji...@apache.org> on 2018/01/15 06:48:00 UTC

[jira] [Created] (LOG4NET-587) Mutex ~ Access to the path is denied in log4net.Appender.RollingFileAppender.ActivateOptions()

Kira Resari created LOG4NET-587:
-----------------------------------

             Summary: Mutex ~ Access to the path is denied in log4net.Appender.RollingFileAppender.ActivateOptions()
                 Key: LOG4NET-587
                 URL: https://issues.apache.org/jira/browse/LOG4NET-587
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 2.0.8
         Environment: Windows Server 2012 R2
            Reporter: Kira Resari


I have recently updated my log4net version from a really old Version (1.2.13) to the newest version, but ever since then, a component of my apache website service throws the following error message:
{code:java}
2018-01-15 06:19:35,933 DEBUG - Exception-Message: Access to the path 'C__Netfira_LeanBuyer_logs_NFDocumentDataLayer2.log' is denied.
2018-01-15 06:19:35,933 DEBUG - Exception-StackTrace:    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.Threading.Mutex.MutexTryCodeHelper.MutexTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.Mutex.CreateMutexWithGuaranteedCleanup(Boolean initiallyOwned, String name, Boolean& createdNew, SECURITY_ATTRIBUTES secAttrs)
   at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name, Boolean& createdNew, MutexSecurity mutexSecurity)
   at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name)
   at log4net.Appender.RollingFileAppender.ActivateOptions()
   at NFCommonImplementation.Logging.InternalLog4NetLoggerFactory.LoggerImpl..ctor(String name)
   at NFCommonImplementation.Logging.InternalLog4NetLoggerFactory.CreateLogger(ILoggerRepository repository, String name)
   at log4net.Repository.Hierarchy.Hierarchy.GetLogger(String name, ILoggerFactory factory)
   at log4net.Repository.Hierarchy.Hierarchy.GetLogger(String name)
   at log4net.Core.LoggerManager.GetLogger(Assembly repositoryAssembly, String name)
   at log4net.LogManager.GetLogger(String name)
   at NFCommonImplementation.Logging.Log4NetFactory.build(LogName id)
   at NFDocumentDataLayer.DocumentDao.probeDocumentList2(DateTime dateStart, DateTime dateEnd, String headStatus, String transmissionStatus, String supplier, String documenttype, String documentsubtype, Int32 processed, String clientId, String documentUser)
   at NFIISWebService.Services.probe(String base64request){code}
Since the crux of the problem seems to be happening inside a log4net function call, I figured I'd post this here. Or is there already a workaround for this?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)