IIS 6.0 and Closing response ends thread

Hello, I don't know if this is an IIS issue or something else, but basically, I wrote a web application in c# that ends the response at a certain point, but then the thread/process still continues to do some processing (rather than forcing the client to wait until all processing is done, it ends the response and then processes).

On my local test machine (Windows 2003 Server, IIS 6.0), when I install the web application and test it, it works perfectly (the thread/process stays alive to complete the processing after it ends the request).

PROBLEM: On the actual server I would like to use, (same configuration as far as I know), the response thread/process immediately ends after it ends the response.

Does anyone know how I can prevent this? I have looked the configuration from both servers (my local test server and the actual server) and they seem identical. I don't know if maybe my local test machine has a bug (and it should act like the server, killing my thread as soon as the response ended), or if the actual machine has a bug, or if there is another setting I am missing that I need to change.

Note: The application pools are identical for this web application on both servers. (i.e. on both, Worker recycling is turned off)

If anyone has any ideas, this will greatly appreciated! Thanks in advance!

I don't have IIS6, I'm not sure what to suggest. I'm not even sure you can make any assumptions about IIS's process threading, it may change internally anyway.

Thanks for the response. (Sorry this post is so late, I've been busy).

I finally ended up just redoing my web application so that it passes off processing to another (NON-WEB, independent) process (I just made a Windows service since I know that has thread reliability and stability as long as you don't run out of event log space).