-
Notifications
You must be signed in to change notification settings - Fork 337
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
InvalidOperationException: Can't replace active reader in 2.2.5 #1469
Comments
@Kation Please provide sample code that reproduces the problem, or trace-level logging that indicates the events leading up to the failure. |
Currently we do not have trace-level logging on production environment. 2.3.5 Stacktrace:
|
We've also observed this problem. In our case the problem has been observed after MySql server has been taken down for a maintenance. Attempts to reproduce locally did not produce the same error for now. In all cases the active reader exception has been wrapped up in As per logs, we have the following: MySqlConnector.MySqlException (0x80004005): Connection was killed
Then, during server downtime we've observed both MySqlConnector.MySqlException (0x80004005): Max connect timeout reached while reaching hostgroup 1 after 10000ms
and System.InvalidOperationException: Can't replace active reader.
Sometimes stack for the same exception (and, seemingly, location) would include a previous location (see at the end) System.InvalidOperationException: Can't replace active reader. (with previous location)
After DB server came back up, |
But if an exception were thrown, the |
I'm having the same issue from time to time with Pomelo.EntityFrameworkCore.MySql 8.0.1, which uses MySqlConnector 2.3.5
|
I'm having the same issue from time to time with Pomelo.EntityFrameworkCore.MySql 8.0.2, which uses MySqlConnector 2.3.5 |
It took an terrifying combination of reusing an existing |
I have a fix ready for testing in 2.4.0 Beta 2. I would greatly appreciate it if everyone who has reported this bug could install and test this version (to confirm the fix) before 2.4.0 ships.
|
Fixed in 2.4.0. |
From @Kation:
Same issues with 2.2.5
Originally posted by @Kation in #1154 (comment)
The text was updated successfully, but these errors were encountered: