-
-
Notifications
You must be signed in to change notification settings - Fork 158
Possible bug: NullReferenceException during request processing #727
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
Comments
Thanks a lot for reporting this! |
Sorry, is JADNC abbreviation of JsonApiDotNetCore? :) If yes, then v4.0.0alpha4. I also tried the source from the master branch of this repo. |
I confirm, same problem on same version. |
Serious bug indeed. I can repro this and believe I have found the root cause. Will work on a fix tomorrow. |
Description
If there are simultaneous requests to an app then sometimes there is NullReferenceException accrues while creation of FilterService. The currentRequest._resourceContex parameter of the constructor is null.
This error is not stable. In most cases, it occurs after the application is started. After some number of requests, it disappears. But if you restart the application it will be again.
I tried this on macOS system and not tried on windows.
...
To reproduce:
I found this in my project, but if you take the GettingStarted example the result will be the same. Start the GettingStarted project and run simultaneous requests. (For example, for nix like system:
$ echo http://localhost:5001/api/articles http://localhost:5001/api/articles | xargs -P 10 -n1 curl
)
There will be an exception.
Environment
The text was updated successfully, but these errors were encountered: