Repository navigation
Session dispose exception #305
Description
DO 7.0
Sorry, can not reproduce in test environment
Catch this exception three times
System.ArgumentNullException: Value cannot be null. (Parameter 'node')
at System.Collections.Generic.LinkedList`1.ValidateNode(LinkedListNode`1 node)
at Xtensive.Collections.TopDeque`2.PopBottom() in /_/Orm/Xtensive.Orm/Collections/TopDeque.cs:line 180
at Xtensive.Caching.LruCache`2.Clear() in /_/Orm/Xtensive.Orm/Caching/LruCache{TKey, TItem}.cs:line 159
at Xtensive.Orm.Session.DisposeImpl(Boolean isAsync) in /_/Orm/Xtensive.Orm/Orm/Session.cs:line 661
at Xtensive.Orm.Session.Dispose() in /_/Orm/Xtensive.Orm/Orm/Session.cs:line 614
System.InvalidOperationException: The LinkedList node does not belong to current LinkedList.
at System.Collections.Generic.LinkedList`1.ValidateNode(LinkedListNode`1 node)
at Xtensive.Collections.TopDeque`2.PopBottom() in /_/Orm/Xtensive.Orm/Collections/TopDeque.cs:line 180
at Xtensive.Caching.LruCache`2.Clear() in /_/Orm/Xtensive.Orm/Caching/LruCache{TKey, TItem}.cs:line 159
at Xtensive.Orm.Session.DisposeImpl(Boolean isAsync) in /_/Orm/Xtensive.Orm/Orm/Session.cs:line 661
at Xtensive.Orm.Session.Dispose() in /_/Orm/Xtensive.Orm/Orm/Session.cs:line 614
Metadata
Metadata
Assignees
Labels
No labels
Activity
alex-kulakov commentedon Mar 9, 2023
Hello @letarak , so this appears in some conditions on production? Does it fail all the time?
alex-kulakov commentedon Mar 9, 2023
Did the problem appear on a version which was publicly available as a release (7.0.3, 7.0.2 etc.) or it is on latest changes on 7.0 branch? I need the version or the commit in case it was built by you on some commit of 7.0 branch. This is important to identify whether it is old problem or has just appeared.
letarak commentedon Mar 10, 2023
Yes, catch on production, but very rarely (5 times total in 3-4 month)
Precise version 7.0.3
Exception seen only in two blocks of code, each of them use nested session scope
Nested session use entity instance from outer scope
Hope this helps
alex-kulakov commentedon Mar 20, 2023
Hmmm... I'll try to reproduce it but probably it will be a hard-to-catch bug. Thank you for the info. If some additional details appear, please post them.
alex-kulakov commentedon Mar 20, 2023
I stumbled across this post in which it is told that errors like "The LinkedList node does not belong to current LinkedList" in concurrent access. Are you sure that there is no hidden switching between sessions? Do you use Session.Activate() and Session.Current in such cases?
letarak commentedon Mar 21, 2023
No, we do not use Session.Activate()
maybe Session.Current with custom resolver
and this can activate session without our help :)
I need check this