Execution Timeout Problem

[greenb]

Our asp.net web app uses a .NET component (DLL) in the bin directory to call
several stored procedures back to back to perform updates. They don't return
any data. Sometimes the total execution time can take 2-3 minutes, but even
though I have set the executionTimeout in web.config to a high number of
seconds (2400), the request will still time out after 90 seconds. The user
sees a Request timed out error. The app logs a ThreadAborted exception,
[Thread was being aborted].

The web app and the component are compiled in Release mode. I read that you
only have to set one property; executionTimeout or the ScriptTimeout
property in IIS, but not both. Is that true or false?

Thanks for your help,

Mark

 

[Brock Allen]

You should consider redesigning this long running work so the browser isn't
waiting for it to complete. So make a button that initiates the work, then
give the user the ability to refresh the page to see the pending work. To
initiate the work you'll have to kick off another thread somehow (so use
ThreadPool.QueueUserWorkItem, or manually create another thread; there are
pros and cons to each of these approaches). To monitor the pending work you'll
need some other status table in the DB where your user can see if the work
is complete. Once it is, update that table.

Anyway, just an idea on how to rework this long running task....