[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924534#comment-15924534 ] Dan K edited comment on LOG4NET-551 at 3/14/17 4:40 PM: Awesome news!!! Thank you guys so much! I will go add it today via NuGet package and provide feedback! :) was (Author: [email protected]): Awesome news!!! Thank you guys so much! I will go add it today via NuGet package and provide results! :) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924434#comment-15924434 ] Dan K edited comment on LOG4NET-551 at 3/14/17 3:41 PM: Hi Stefan, I see the voting process is complete and positive news! Do you have a timetable as to when this release (v2.0.8) will be cut/available in NuGet? Thanks, Danny was (Author: [email protected]): Hi Stefan, I see the voting process is complete and positive news! Do you have a timetable as to when this release will be cut/available in NuGet? Thanks, Danny > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897000#comment-15897000 ] Dan K edited comment on LOG4NET-551 at 3/7/17 2:22 PM: --- Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of testing procedure after upgrade, report any "silent" exceptions/degrades. As a result, we started seeing this exception consistently and noticed it's isolated when file appender is used. We notice a huge difference between messages written to DB (more) vs to file because of these exceptions and file logging losing messages. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners or don't have DB/File logging capabilities to compare that something is wrong. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. was (Author: [email protected]): Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of testing procedure after upgrade, report any "silent" exceptions/degrades. As a result, we started seeing this exception consistently and noticed it's isolated when file appender is used. We notice a huge difference between messages writtent to DB (more) vs to file because of these exceptions and file logging losing messages. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners or don't have DB/File logging capabilities to compare that something is wrong. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899209#comment-15899209 ] Dan K edited comment on LOG4NET-551 at 3/7/17 2:22 PM: --- Hi Stefan, Update: 1) I cloned and built v2.0.8 from latest trunk to upgrade as you suggested. In our case, this is will be for testing purposes only until we get an official release through NuGet. 2) Running a new build of our own software using v2.0.8 since yesterday morning and no more "LockRecursionExceptions". We usually see these immediately with v2.0.7, but wanted to run all day/overnight under heavy load just to make our case. Please let me know if there is anything else you would like us to try to help expedite official release of v2.0.8. We understand/respect this is open source and the process for releases is different, but your help to make this happen is very much appreciated. I am sure others will appreciate this release too as they learn their version could be "silently" throwing this particular exception since version 1.2.12. On Mar 6, 2017 6:11 AM, "Stefan Bodewig (JIRA)" wrote: [ https://issues.apache.org/jira/browse/LOG4NET-551?page=com. atlassian.jira.plugin.system.issuetabpanels:comment-tabpane l&focusedCommentId=15897107#comment-15897107 ] Stefan Bodewig commented on LOG4NET-551: anything that ensures the release will actually fix the problem for you will be good. This issue must have been present since 1.2.12. not allowed in this mode. timeout) timeout) loggingEvent) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) using `log4net.Appender.FileAppender`. curly brackets with square brackets because otherwise JIRA interprets them as macros): ToStringWrapper(parameters)); generating another logging call. But If I put breakpoints at the log call and at the first line of ToStringWrapper.ToString, the exception will show up in the console between those two points. "continuing" and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346) was (Author: [email protected]): Hi Stefan, Update: 1) I cloned and built v2.0.8 from latest trunk to upgrade as you suggested. In our case, this is will be for testing purposes only until we get an official release through NuGet. 2) Running a new build of our own software using v2.0.8 since yesterday morning and no more "LockRecursionExceptions". We usually see these immediately with v2.0.7, but wanted to run all day/overnight under heavy load just to make our case. Please let me know if there is anything else you would like us to try to help expedite official release of v2.0.8. We understand/respect this is open source and the process for releases is different, but your help to make this happen is very much appreciated. I am sure others will appreciate this release too as they learn their version could be "silently" throwing this particular exception since version 1.2.12. On Mar 6, 2017 6:11 AM, "Stefan Bodewig (JIRA)" wrote: [ https://issues.apache.org/jira/browse/LOG4NET-551?page=com. atlassian.jira.plugin.system.issuetabpanels:comment-tabpane l&focusedCommentId=15897107#comment-15897107 ] Stefan Bodewig commented on LOG4NET-551: anything that ensures the release will actually fix the problem for you will be good. This issue must have been present since 1.2.12. not allowed in this mode. timeout) timeout) loggingEvent) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) using `log4net.Appender.FileAppender`. curly brackets with square brackets because otherwise JIRA interprets them as macros): ToStringWrapper(parameters)); generating another logging call. But If I put breakpoints at the log call and at the first line of ToStringWrapper.ToString, the exception will show up in the console between those two points. "continuing" and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899209#comment-15899209 ] Dan K edited comment on LOG4NET-551 at 3/7/17 2:21 PM: --- Hi Stefan, Update: 1) I cloned and built v2.0.8 from latest trunk to upgrade as you suggested. In our case, this is will be for testing purposes only until we get an official release through NuGet. 2) Running a new build of our own software using v2.0.8 since yesterday morning and no more "LockRecursionExceptions". We usually see these immediately with v2.0.7, but wanted to run all day/overnight under heavy load just to make our case. Please let me know if there is anything else you would like us to try to help expedite official release of v2.0.8. We understand/respect this is open source and the process for releases is different, but your help to make this happen is very much appreciated. I am sure others will appreciate this release too as they learn their version could be "silently" throwing this particular exception since version 1.2.12. On Mar 6, 2017 6:11 AM, "Stefan Bodewig (JIRA)" wrote: [ https://issues.apache.org/jira/browse/LOG4NET-551?page=com. atlassian.jira.plugin.system.issuetabpanels:comment-tabpane l&focusedCommentId=15897107#comment-15897107 ] Stefan Bodewig commented on LOG4NET-551: anything that ensures the release will actually fix the problem for you will be good. This issue must have been present since 1.2.12. not allowed in this mode. timeout) timeout) loggingEvent) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) using `log4net.Appender.FileAppender`. curly brackets with square brackets because otherwise JIRA interprets them as macros): ToStringWrapper(parameters)); generating another logging call. But If I put breakpoints at the log call and at the first line of ToStringWrapper.ToString, the exception will show up in the console between those two points. "continuing" and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346) was (Author: [email protected]): Hi Stefan, Update: 1) I cloned and built v2.0.8 from latest trunk to upgrade as you suggested. In our case, this is will be for testing purposes only until we get an official release through NuGet. 2) Running a new build of our own software using v2.0.8 since yesterday morning and no more "LockRecursionExceptions". We usually see these immediately with v2.0.7, but wanted to run all day/overnight under heavy load just to make our case. Please let me know if there is anything else you would like us to try to help expedite official release of v2.0.8. We understand/respect this is open source and the process for releases is different, but your help to make this happen is very much appreciated. On Mar 6, 2017 6:11 AM, "Stefan Bodewig (JIRA)" wrote: [ https://issues.apache.org/jira/browse/LOG4NET-551?page=com. atlassian.jira.plugin.system.issuetabpanels:comment-tabpane l&focusedCommentId=15897107#comment-15897107 ] Stefan Bodewig commented on LOG4NET-551: anything that ensures the release will actually fix the problem for you will be good. This issue must have been present since 1.2.12. not allowed in this mode. timeout) timeout) loggingEvent) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) using `log4net.Appender.FileAppender`. curly brackets with square brackets because otherwise JIRA interprets them as macros): ToStringWrapper(parameters)); generating another logging call. But If I put breakpoints at the log call and at the first line of ToStringWrapper.ToString, the exception will show up in the console between those two points. "continuing" and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLoc
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/7/17 12:49 AM: Hi Stefan, here is more context around our experience with v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use for upcoming release. 2) We haven't seen this exception until the upgrade to v2.0.7 and wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. 3: This is the exception we see with log4net internal debugging on using v2.0.7: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) was (Author: [email protected]): Hi Stefan, here is more context around our experience with v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We haven't seen this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote}
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/6/17 9:07 PM: --- Hi Stefan, here is more context around our experience with v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We haven't seen this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. was (Author: [email protected]): Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We haven't seen this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:43 PM: --- Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We haven't seen this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. was (Author: [email protected]): Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > e
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897000#comment-15897000 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:35 PM: --- Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of testing procedure after upgrade, report any "silent" exceptions/degrades. As a result, we started seeing this exception consistently and noticed it's isolated when file appender is used. We notice a huge difference between messages writtent to DB (more) vs to file because of these exceptions and file logging losing messages. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners or don't have DB/File logging capabilities to compare that something is wrong. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. was (Author: [email protected]): Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of our normal testing after upgrade, to see if there were any "silent" exceptions/degrades. As a result, we started seeing this exception consistently and noticed it's isolated to file logging when file appender is used. We notice a huge difference between messages writtent to DB (more) vs to file because of these exceptions and file logging losing messages. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners or don't have DB/File logging capabilities to compare that something is wrong. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:32 PM: --- Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. was (Author: [email protected]): Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. Then we could have addressed this sooner. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Lev
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:31 PM: --- Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. Then we could have addressed this sooner. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we're confident that the fix in v2.0.8 will help us get past this block and move forward. was (Author: [email protected]): Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. Then we could have addressed this sooner. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we strongly feel that the fix in v2.0.8 will help us get past this block and move forward. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Ty
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:30 PM: --- Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. Then we could have addressed this sooner. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7 for file logging: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we strongly feel that the fix in v2.0.8 will help us get past this block and move forward. was (Author: [email protected]): Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. Then we could have addressed this sooner. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we strongly feel that the fix in v2.0.8 will help us get past this block and move forward. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStac
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897000#comment-15897000 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:26 PM: --- Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of our normal testing after upgrade, to see if there were any "silent" exceptions/degrades. As a result, we started seeing this exception consistently and noticed it's isolated to file logging when file appender is used. We notice a huge difference between messages writtent to DB (more) vs to file because of these exceptions and file logging losing messages. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners or don't have DB/File logging capabilities to compare that something is wrong. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. was (Author: [email protected]): Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of our normal testing after upgrade, to see if there were any "silent" exceptions/degrades. As a result, we started seeing this exception consistently and noticed it's isolated to file logging when file appender is used. We notice a huge difference between messages writtent to DB (more) vs to file because of these exceptions and file logging losing messages. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897000#comment-15897000 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:25 PM: --- Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of our normal testing after upgrade, to see if there were any "silent" exceptions/degrades. As a result, we started seeing this exception consistently and noticed it's isolated to file logging when file appender is used. We notice a huge difference between messages writtent to DB (more) vs to file because of these exceptions and file logging losing messages. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. was (Author: [email protected]): Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of our normal testing after upgrade, to see if there were any "silent" exceptions occuring, and sure enough we see this one. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:19 PM: --- Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. Then we could have addressed this sooner. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) 4. With all the evidence we have so far around this particular exception, we strongly feel that the fix in v2.0.8 will help us get past this block and move forward. was (Author: [email protected]): Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I w
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897243#comment-15897243 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:15 PM: --- Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We didn't see this exception until the upgrade to v2.0.7. We wouldn't have known about this error prior since it wasn't present in 1.2.11, which is consistent with your last comment. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) was (Author: [email protected]): Hi Stefan, here is a little more background/detail/context with issue we are currently seeing in v2.0.7: 1) During latest development cycle, we upgraded straight from version 1.2.11 to v2.0.6, then the same week to v2.0.7 with intent to use the latest version for upcoming release. As you are aware, there have many bugs fixed/improvements made since 1.2.11. 2) We didn't see this exception until the upgrade to v2.0.7 which coincides with your last comment and also what the latest fix in v2.0.8 addresses (LockExcursionException). We wouldn't have known about this error prior since it wasn't present in 1.2.11. I wasn't involved in the logging development efforts during that time and not sure why this wasn't upgraded sooner. 3: Here is the consistent/only exception we see with log4net internal debugging on using v2.0.7: log4net:ERROR Exception while logging System.Threading.LockRecursionException: Recursive read lock acquisitions not allowed in this mode. at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout) at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker timeout) at log4net.Util.ReaderWriterLock.AcquireReaderLock() at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent loggingEvent) at log4net.Repository.Hierarchy.Logger.ForcedLog(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) at log4net.Repository.Hierarchy.Logger.Log(Type callerStackBoundaryDeclaringType, Level level, Object message, Exception exception) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macr
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897000#comment-15897000 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:13 PM: --- Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of our normal testing after upgrade, to see if there were any "silent" exceptions occuring, and sure enough we see this one. Others probably haven't reported it because they aren't enabling internal debugging/trace listeners. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. was (Author: [email protected]): Upgrading should be a good thing, which is why we didn't mind going to v2.0.7 initially. Log4net is our go-to for both file logging/db logging and as part of our normal testing after upgrade, to see if there were any "silent" exceptions occuring, and sure enough we see this one. Other's probably haven't reported it because they aren't enabling internal debugging/trace listeners. I will post the exception we see as well here to further uphold our findings and perhaps help others that experience same thing. I can build the dependency from trunk just to verify the fix addresses it, but we see that when the appender is called that it can't recursively log when using the default policy in .net 4.0/above, which the fix in v2.0.8 addresses. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896931#comment-15896931 ] Dan K edited comment on LOG4NET-551 at 3/6/17 1:12 PM: --- Stefan, that doesn't seem very reasonable. Especially, given any time this particular exception occurs, log event/messages are completely lost. That is completely unacceptable in a production setting. I would think at the very least, now that this issue has been made aware of, some sort of hot fix/patch for v2.0.7 become "officially" available if v2.0.8 has to wait. If I recall correctly, one minor bug found in v2.0.6 triggered an immediate fix/release through NuGet and made available that same week (v2.0.7). Why would this be handled any different? Again, the alternative methods mentioned in this thread aren't a viable option. was (Author: [email protected]): Stefan, that doesn't seem very reasonable. Especially, given any time this particular exception occurs, log event/messages are completely lost. That is completely unacceptable in a production setting. I would think at the very least, now that this issue has been made aware of, some sort of hot fix/patch for v2.0.7 become "officially" available if v2.0.8 has to wait. If I recall correctly, one minor bug found in v2.0.6 triggered an immediate fix/release through NuGet and made available that same week (v2.0.7). Why would something as important as this be handled any different? Again, the alternative hacks mentioned in this thread aren't a viable option. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896931#comment-15896931 ] Dan K edited comment on LOG4NET-551 at 3/6/17 9:05 AM: --- Stefan, that doesn't seem very reasonable. Especially, given any time this particular exception occurs, log event/messages are completely lost. That is completely unacceptable in a production setting. I would think at the very least, now that this issue has been made aware of, some sort of hot fix/patch for v2.0.7 become "officially" available if v2.0.8 has to wait. If I recall correctly, one minor bug found in v2.0.6 triggered an immediate fix/release through NuGet and made available that same week (v2.0.7). Why would something as important as this be handled any different? Again, the alternative hacks mentioned in this thread aren't a viable option. was (Author: [email protected]): Stefan, that doesn't seem very reasonable. Especially, given any time this particular exception occurs, log event/messages are completely lost. That is completely unacceptable in a production setting. I would think at the very least, now that this issue has been made aware of, some sort of hot fix/patch for v2.0.7 become "officially" available if v2.0.8 has to wait. If I recall correctly, one minor bug found in v2.0.6 triggered an immediate fix/release through NuGet and made available that same week. Why would something as important as this be handled any different? Again, the alternative hacks mentioned in this thread aren't a viable option for us. I'm sure other's in the same boat whom are using v2.0.7, won't be happy either. Just because log4net fails "silently" I wouldn't think that translates to prolonging releases. > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Dan K edited comment on LOG4NET-551 at 3/4/17 6:46 PM: --- Hi Stefan, thank you for the fast response and invaluable information. When is v2.0.8 expected to be released? Building it ourselves isn't a preferred option to upgrade. We have an upcoming release and rely on NuGet for packages for upgrades. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. We would love to take advantage of "all" the fixes/improvements in v2.0.8. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages. We would love to take advantage of "all" the fixes/improvements in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 7:34 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages. We would love to take advantage of "all" the fixes in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages. We would love to have all the fixes in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 7:35 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages. We would love to take advantage of "all" the fixes/improvements in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages. We would love to take advantage of "all" the fixes in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 7:07 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages. We would love to have all the fixes in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages and would love to have all the fixes in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 7:07 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages and would love to have all the fixes in v2.0.8. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages (latest versions). Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 6:22 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release and rely on NuGet for packages (latest versions). Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release ourselves and rely on NuGet for packages (latest versions). Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894674#comment-15894674 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 6:08 PM: Hi, we recently updated to Log4net version 2.0.7 and also experiencing the "LockRecursionException". I see the above PR (https://issues.apache.org/jira/browse/LOG4NET-550) covers .Net Framework 4.0, but does it also support .Net 4.5/above? I confirmed the log4net version (2.0.7) we are using is against .Net 4.5 when we see the errors. Your feedback/help is much appreciated before we upgrade to 2.0.8! Thanks! :) was (Author: [email protected]): Hi, we recently updated to Log4net version 2.0.7 and also experiencing the "LockRecursionException". I see the above PR (https://issues.apache.org/jira/browse/LOG4NET-550) covers .Net Framework 4.0, but does it also support .Net 4.5? I confirmed the log4net version (2.0.7) we are using is against .Net 4.5 when we see the errors. Your feedback/help is much appreciated before we upgrade to 2.0.8! Thanks! :) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 6:02 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release ourselves and rely on NuGet for packages (latest versions). Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I see in previous comments that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release ourselves and rely on NuGet for packages (latest versions). Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I read somewhere that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 6:00 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't a preferred option. We have an upcoming release ourselves and rely on NuGet for packages (latest versions). Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I read somewhere that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't an option since we have an upcoming release ourselves and rely on NuGet for packages. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I read somewhere that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894769#comment-15894769 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 5:58 PM: Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't an option since we have an upcoming release ourselves and rely on NuGet for packages. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I read somewhere that this was an alternative workaround. Thanks again! was (Author: [email protected]): Hi Stefan, thank you for the fast response and invaluable information. When is this expected to be released? Building it ourselves isn't an option since we have an upcoming release ourselves. Also, reverting to log4net v2.0.7 to use .Net Framework 3.5 isn't an option. I read somewhere that this was an alternative workaround. Thanks again! > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894674#comment-15894674 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 4:42 PM: Hi, we recently updated to Log4net version 2.0.7 and also experiencing the "LockRecursionException". I see the above PR (https://issues.apache.org/jira/browse/LOG4NET-550) covers .Net Framework 4.0, but does it also support .Net 4.5? I confirmed the log4net version (2.0.7) we are using is against .Net 4.5 when we see the errors. Your feedback/help is much appreciated before we upgrade to 2.0.8! Thanks! :) was (Author: [email protected]): Hi, we recently updated to Log4net version 2.0.7 and also experiencing the "LockRecursionException". I see the above PR (https://issues.apache.org/jira/browse/LOG4NET-550) addresses it for .Net Framework 4.0, but does it also support .Net 4.5? I confirmed the log4net version (2.0.7) we are using is against .Net 4.5 when we see the errors. Your feedback/help is much appreciated before we upgrade to 2.0.8! Thanks! :) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (LOG4NET-551) LockRecursionException when using File Appenders
[ https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894674#comment-15894674 ] Danny Klausner edited comment on LOG4NET-551 at 3/3/17 4:34 PM: Hi, we recently updated to Log4net version 2.0.7 and also experiencing the "LockRecursionException". I see the above PR (https://issues.apache.org/jira/browse/LOG4NET-550) addresses it for .Net Framework 4.0, but does it also support .Net 4.5? I confirmed the log4net version (2.0.7) we are using is against .Net 4.5 when we see the errors. Your feedback/help is much appreciated before we upgrade to 2.0.8! Thanks! :) was (Author: [email protected]): Hi, we recently updated to Log4net version 2.0.7 and also experiencing the "LockRecursionException". I see the above PR (https://issues.apache.org/jira/browse/LOG4NET-550) addresses it for .Net Framework 4.0, but does it also support 4.5? I confirmed the log4net version (2.0.7) we are using is against .Net 4.5 when we see the errors. Your feedback/help is much appreciated before we upgrade to 2.0.8! Thanks! :) > LockRecursionException when using File Appenders > > > Key: LOG4NET-551 > URL: https://issues.apache.org/jira/browse/LOG4NET-551 > Project: Log4net > Issue Type: Bug >Affects Versions: 2.0.7 >Reporter: Matthew Lefoster >Priority: Minor > Fix For: 2.0.8 > > > I have been getting the following exception on the console: > {quote} > log4net:ERROR Exception while logging > System.Threading.LockRecursionException: Recursive read lock acquisitions not > allowed in this mode. >at > System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeoutTracker > timeout) >at System.Threading.ReaderWriterLockSlim.EnterReadLock() >at log4net.Util.ReaderWriterLock.AcquireReaderLock() >at log4net.Repository.Hierarchy.Logger.CallAppenders(LoggingEvent > loggingEvent) >at log4net.Repository.Hierarchy.Logger.ForcedLog(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) >at log4net.Repository.Hierarchy.Logger.Log(Type > callerStackBoundaryDeclaringType, Level level, Object message, Exception > exception) > {quote} > I have a number of different appenders, but this only happens when I am using > `log4net.Appender.FileAppender`. > Using a debugger, I was able to narrow it down to this line (I replaced curly > brackets with square brackets because otherwise JIRA interprets them as > macros): > {quote} > Logger.DebugFormat("[1] Executing SQL: [0][2][0]With parameters: [3]", > Environment.NewLine, methodName, sql, new > ToStringWrapper(parameters)); > {quote} > My first thought was that ToStringWrapper() was throwing an exception or > generating another logging call. But If I put breakpoints at the log call and > at the first line of ToStringWrapper.ToString, the exception will show up in > the console between those two points. > Oddly enough, if I "step into" the logging call instead of just "continuing" > and letting the breakpoints handle it, no exception happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
