Last post Mar 14, 2019 02:38 AM by Nan Yu
Mar 12, 2019 12:06 PM|nambir|LINK
In our application we got the error "The request queue limit of the session is exceeded."
i need two info
1) From where i can check there is increase in the number of request, so this error is caused.
ie. Which part of the Application server cause the issue. I need to find out why the error came suddenly. So i have some metrics.
2) What is the solution for this error.
Mar 12, 2019 12:31 PM|PatriceSc|LINK
You tried F12 Network ? Seems related to doing too many requests from a single browser session. Could it be that you have tons of Ajax calls launched behind the scene ?
Edit: seems related to
Still before doing a config change I would prefet to see if the root cause couldn't be fixed such as not using session for web services when it is not needed or redesigning an API (for example if you often need to get data for a whole list of ids it could
be best to have an API allowing to retrieve that in one call rather than having to call an API for each and every id in a list).
Mar 13, 2019 06:54 AM|nambir|LINK
Thanks for the reply.
Which tool i can use in the server to check " tons of Ajax calls launched behind the scene ?"
Because we dont know which page is causing this issue.
It is happening in PROD, i am not sure which page the customer is browsing which lead to this issue.
Mar 14, 2019 02:38 AM|Nan Yu|LINK
Hi nambir ,
Do you tried to add logging to your application. Most logging frameworks like log4net,ELMAH offers another approach to logging runtime errors in a production environment:
And do you tried to increase RequestQueueLimitPerSession setting :
<add key="aspnet:RequestQueueLimitPerSession" value="2147483647"/>