Open hunterbdoerr opened 1 month ago
In your connection string, do you have MultipleActiveResultSets
set to true?
Please see an example connection string here.
The connection string sets MultipleActiveResultSets=false
.
Is there a reason you can't set it to true? If you do that it'll probably resolve your issue.
Jumping in here since @hunterbdoerr and I are contributors on the same project.
We had been hesitant to move forward with that solution given that connection string is shared with other projects. The primary identified source of risk comes from transaction savepoints being disabled when MARS is enabled as documented here for EF functionality..
That being said, enabling MARS does seem to resolve this issue, and we can try to work around the other identified risk areas. However, if there are any other known solutions or other ways of approaching this issue, any additional information would be greatly helpful.
Which version of Duende IdentityServer are you using? 6.0
Which version of .NET are you using? 6.0
Describe the bug When calling the GET
token
endpoint, there is an occasionalMultipleActiveResultSets
exception thrown.Reading information about the specific error message unrelated to this workflow, the most common culprit is an async method that is not awaited. This would occur in the same transient dbcontext created for the request attempting to execute a request on top of itself.
Log output/exception with stacktrace