Skip to content
Discussion options

You must be logged in to vote

It shouldn't. Previously we had some coding mistakes that sporadically resulted in such errors, but that shouldn't be the case (at least with 2.1.x). This error is raised when two threads use the same ISession, i.e. you have multi-threaded code (executing withing the same request) and an ISession instance is shared among them.

You can set EnableThreadSafetyChecks to make YesSql throw an explicit exception when this happens, with details about the two threads, see https://docs.orchardcore.net/en/latest/reference/modules/Data/#configuring-yessql.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by weirdyang
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants