Have Geek Brain

Basic question about request queues in IIS / ASP.Net

I have an ASP.Net application running under IIS 6. On a simple page, there are two radio buttons and a submit button. If I select the "A" radio button and submit the page, a long PDF is generated that takes about a minute. If I select the "B" radio button, a small PDF is generated. (In both cases, the PDF is written out to a Response object and opened in my browser.)

If I select radio button "A" and submit, then press the red "X" in my browser to stop the current request, then select radio button "B" and send again, this page still takes a long time to process my request.

Sure, my first request is still being processed on the server, but I was wondering how IIS and / or ASP.Net queue my requests to ensure fair use of servers among all users. Am I correct in assuming this is happening, and if so, how is it done?

+2


a source to share


1 answer


You are probably facing a session lock. Try to run the experiment in multiple browsers i.e. Instead of stopping the browser and resubmitting, run both requests in separate browsers (like Firefox and Chrome), which will use a separate session and therefore won't be blocked.



See Concurrent Queries and Session State for a rationale and workarounds.

+1


a source






More articles:


All Articles