-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading is not allowed after reader was completed #2692
Comments
It sounds like the connection is being used post-disposal here (at which point we shouldn't be sending any more commands) - is that accurate? |
@NickCraver so the application has one instance of In the screenshot above it looks like we actualy handle this OK when reading but if |
Hi,
We are getting the following exception intermittently in production:
When this happens its alway after we have called
IDatabase.StreamAddAsync
.Looking at PhysicalConnection I'm wondering if there is a race condition between
ReadFromPipe
and something callingDispose
?Does that make sense? I'm pretty sure this class is used by multiple threads and so I think the above is posslbe. Looking at the exception handler it seems like we don't even really want to report this exception?
So to sum up:
We have seen this happen on multiple OS, dotnet, and package versions:
Let me know if you need more info.
Thanks!
The text was updated successfully, but these errors were encountered: