asked on
IIS 8.5 Long running requests block other requests for minutes (they wait in request queue)
Hi
Environment: Windows 2012R2 Server, IIS 8.5
I have a classic .asp script which uses "wscrip.shell" to call an external .exe to create LARGE .zip files on the fly and send them to the client browser. While this process is running, other requests to the server are blocked (well they stay in the queue) but this is not acceptable for minutes. I already increased the maximum number of worker processes in the advanced settings of the application pool associated with the site. But like this, I loose my sessions, because they are tied to the worker process. A following page request could be processed by any of the worker processes and session state seems not to be shared amongst the worker processes. Thefore the user possibly looses it's session variables with each page request. Re-Designing the application without sessions would be possible but taking to long in actual emergency.
ANY BETTER SOLUTIONS?
Environment: Windows 2012R2 Server, IIS 8.5
I have a classic .asp script which uses "wscrip.shell" to call an external .exe to create LARGE .zip files on the fly and send them to the client browser. While this process is running, other requests to the server are blocked (well they stay in the queue) but this is not acceptable for minutes. I already increased the maximum number of worker processes in the advanced settings of the application pool associated with the site. But like this, I loose my sessions, because they are tied to the worker process. A following page request could be processed by any of the worker processes and session state seems not to be shared amongst the worker processes. Thefore the user possibly looses it's session variables with each page request. Re-Designing the application without sessions would be possible but taking to long in actual emergency.
ANY BETTER SOLUTIONS?
Microsoft IIS Web ServerServer HardwareWindows Server 2012Windows OSServer Software
Last Comment
Dan McFadden
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Has the reconfiguration resolved the issue?
Dan
Dan
ASKER
yes, it worked. But was quite a bunch of program changes and testing. I did it already 2 weeks ago, was urgent. I just had hope it could be just an IIS configuration issue. I had noted it worked in spring 2016 and I was completely surprised why it didn't anymore suddenly.
Glad it's working then. I guess you could close the question then.
Dan
Dan
Thanks