Recursive read lock acquisitions not allowed in this mode.
Closed this issue · 5 comments
Description
at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout)
at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeSpan timeout)
at LiteDB.Engine.LockService.EnterTransaction()
at LiteDB.Engine.TransactionMonitor.GetTransaction(Boolean create, Boolean queryOnly, Boolean& isNew)
at LiteDB.Engine.LiteEngine.AutoTransaction[T](Func`2 fn)
at LiteDB.Engine.LiteEngine.Insert(String collection, IEnumerable`1 docs, BsonAutoId autoId)
at LiteDB.LiteCollection`1.Insert(T entity)
at WatchDog.src.Helpers.LiteDBHelper.InsertWatchLog(WatchLog log)
at WatchDog.src.Managers.DynamicDBManager.InsertWatchLog(WatchLog log)
at WatchDog.src.WatchDog.InvokeAsync(HttpContext context)
at Serilog.AspNetCore.RequestLoggingMiddleware.Invoke(HttpContext httpContext)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
at WatchDog.src.WatchDogExceptionLogger.InvokeAsync(HttpContext context)
To Reproduce
I started a new .NET 8 project and added WatchDog and I get these errors everywhere.
Expected behavior
No LiteDB errors?
Screenshots
If applicable, add screenshots to help explain your problem.
Details (please complete the following information):
- Project Type: Razor Pages
- Framework Version .NET 8
- WatchDog Version 1.4.10
- Database LiteDB
- Browser Chrome
Additional context
Add any other context about the problem here.
This issue is stale because it has been open for 30 days with no activity.
Bump.
This issue is stale because it has been open for 30 days with no activity.
Bump
Hi @VictorioBerra ,
This is currently an open issue with the LiteDB dependency and we are following up with it.
However, a potential workaround has been released with the new version (v1.4.11). Do let us know if the issue still persists.