You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jinhuafei edited this page Apr 2, 2018
·
1 revision
Title
A short description of the bug that becomes the issue title
e.g. SqlSessionStateProviderAsync throws ArgumentOutOfRangeException when there are too many requests
Functional impact
Does the bug result in any actual functional issue, if so, what?
e.g. Yes. When this happens, the sessionstate data won't be saved into sql server.
Minimal repro steps
What is the smallest, simplest set of steps to reproduce the issue. If needed, provide a project that demonstrates the issue.
Create a web application project targeting 4.6.2
install SqlSessionStateProviderAsync 1.0.1 nupkg and configure it
Write Session data in an aspx
Send 100+ concurrent requests with same sessionId
Expected result
What would you expect to happen if there wasn't a bug
e.g. The session data is saved into sql server
Actual result
What is actually happening
e.g. Got ArgumentOutOfRangeException