My IIS log has a small percentage of hits where Time-taken are well over 90 seconds. (Up to 800 seconds, in fact!)
How can this be, when the database timout is set to 30 seconds and the IIS script timeout is set to 90 seconds?
When I run the pages with heavy queries from a browser, it sometimes does time out and generate an error after 30 seconds. But it does not run for 800 seconds!
Are these log file records erroneous somehow? Or does SQL Server continue to run the query after the timeout error is generated?
Another strange thing... Some of these large time-takens are pages with no db queries whatsoever. How can a simple ASP page with no db calls take 200 seconds to execute when normally it takes less than 2 seconds? There does not appear to be a pile up. Other pages are loading normally at that same point in time.
In addition, I get a smaller number of hits that do generate the timeout errors:
These are maxed at 30 seconds time-taken. I would expect all my "too-heavy" queries to generate this result instead of the former results.
Has anyone else seen this in their logs? How do I make sense of it?