-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Check commands[i] is not null for avoid NRE on Dispose command #22921
Comments
I expect all this code will change as part of #14044, but feel free to submit a PR in the meantime. |
Is there any workaround to this? I'm hitting this even in development. |
Also we face with next Exception. We can't any Commit or Rollback transaction. Could you help me with any workaround?
|
Are you using the same connection on multiple threads? ADO.NET objects are generally not thread safe. |
Just saw this on a local run of the EF tests:
|
Note that this is because the test is re-using the same connection on multiple threads concurrently. |
Fixes #22921 Note that the reports here seem to be caused by incorrect use by the same connection concurrently. This is invalid. However, made the code a bit more robust here anyway.
Fixes #22921 Note that the reports here seem to be caused by incorrect use by the same connection concurrently. This is invalid. However, made the code a bit more robust here anyway.
@bricelam FYI
Sometimes in inner collection _commands can be null value
The text was updated successfully, but these errors were encountered: