jquery .ajax request blocked by long running .ajax request

I am trying to use jQuery's .ajax functionality to make a progress bar.

A request is submited via .ajax, which starts a long running process. Once submited another .ajax request is called on an interval which checks the progress of this process. Then a progress meter is updated using this information.

However开发者_运维知识库, the progress .ajax call only returns once the long running process has completed. Its like its being blocked by the initial request.

The weird thing is this process works fine on dev but is failing on the deployment server. I am running on IIS using ASP.Net MVC.

Update: Apparently, it is browser related because it is working fine on IE 7 but is not working on IE 8. This is strange because IE 8 allows up to 6 connections on broadband where IE 7 only allows 2 requests per domain.

Update2: I think it's a local issue because it appears to be working fine on another IE 8 machine.

The server will only run one page at a time from each user. When you send the requests to get the progress status, they will be queued.

The solution is to make the page that returns the status sessionless, using EnableSessionState="false" in the @Page directive. That way it's not associated with any user, so the request isn't queued.

This of course means that you can't use session state to communicate the progress state from the thread running the process to the thread getting the status. You have to use a different way of keeping track of running processes and send some identifier along with the requests that gets the status so that you know which user it came from.

Some browsers (in particular, IE) only allows two requests to the same domain at the same time. If there are any other requests happening at the same time, then you might run into this limitation. One way around it is to have a few different aliases for the domain (some sites use "www1.example.com" and "www2.example.com", etc)

You should be able to use Firebug or Fiddler to determine how many requests are in progress, etc.

Create an Asynchronus handler (IHttpAsyncHandler) for your second ajax request.

use any parameter required via the .ashx querystring in order to process what you want because the HttpContext won't have what you'll need. You barely will have access to the Application object.

Behind the scenes ASP.NET will create for you a thread from the CLR pool, not the application pool, so You'll have an extra performance gain with IHttpAsyncHandler