IIS 7 and Above
Application Request Routing (ARR)
Arr to IIS aspx app (ASP.NET Session ID)
Last post Aug 01, 2018 07:36 AM by Rovastar
May 30, 2018 12:51 AM|fben|LINK
Hello, good evening, everyone. I am incorporating an ARR server to blanve two IIS application servers (aspx). The question is that when I pass the requests through the and I route them to a server farm, in the IIS that hosts the application
I have problems that indicate this.
Multiple requests in the process state with the same ASP.NET Session ID were detected in the dump file. At any point of time, ASP.NET executes only one request
with the same session id and the remaining requests are queued behind the request which is getting executed.
Please check why you got more than one request for the same ASP.NET Session ID by viewing the
HTTP report and the ASP.NET Session ID Report</div> <div class="group mt20"></div> <div class="group mt20">
It is clear that the incorporation of the ARR is generating problems with the session, but I can not figure out how to solve it. From what I understand, multiple sessions are being generated and asp.net is slow to release / resolve them Session
Id: yegprd55dygtuv45nt4ohg45 Requests: 21
Thank you very much, I hope you can help me.
Jun 07, 2018 01:03 AM|deepakpanchal10|LINK
If you don't use ARR then does your project work with out any error?
Did you change any settings in ARR?
Let us know about that, It can help us to narrow down the issue.
Jun 07, 2018 01:44 PM|Rovastar|LINK
Jun 07, 2018 04:23 PM|fben|LINK
Jul 31, 2018 10:19 AM|Mr-Beens|LINK
We have the same problem here and we found out IIS ARR caches dynamic content by default. It caches also a request to a resource (like a aspx page or a ashx handler) for users which didn't have a Session ID cookie already. The cookie is set by the response
headers and that response is cached in IIS ARR for other users also.
Now, when a second user request the same resource it gets the cached one and its session cookie changes to the same one as user 1 already received.
This link explains output caching and documents the available strategies to solve the problem. We are currently in testing stage to solve this issue.
Aug 01, 2018 07:36 AM|Rovastar|LINK