Hi everyone,



I have some very long-running pages (doing bulk-inserts of uploaded

data)...I have changed executionTimeout property in <httpRuntime> to

1800 (half an hour), however, the aspnet_wp.exe is recycled after 3

minutes, because of responseDeadlockInterval in <processModel> element

in machine.config.  Now, this should only happen when there are queued

requests and aspnet_wp.exe is not responding at all...How can a single

request, which is consuming only a single thread, block the whole

application? All machine.config settings are on their default settings

(25 worker threads, 25 I/O threads, etc.)...



Any ideas?



Thanks in advance,

Stan



P.S. I know I should run this in the business layer on its own thread

rather than running it in the context of the page, and I will, but the

problem of the worker process restarting in case of long-running pages

is still an issue nonetheless...