In a legacy ASP application we have some web pages that do some routine maintenance - precalculating some tables, deleting old data, etc. We schedule the running of these pages through Windows Scheduler. Its a low tech and reliable solution.
One of the pages takes about 12 min to run. It required some maintenance today. So I navigated to the URL to test it - and waited. So I opened up a tab in IE7 to go to another part of the same web site expecting the home page of the site to come up instantly. But it sat there with the thumper thumping, the progress indicator ticking over and no page. Hmmmm.... I opened another web browser and navigated to the home page and it came up instantly.
Back to the first browser on the second tab. Clicked Stop and Go - still nothing. After about 3 min the home page eventually turned up. I created other tabs and navigated to other sites OK.
I reproduced it a second time.
Why would IE have a problem opening up a socket connection to web site that is being accessed on another tab - very, very strange.
No comments:
Post a Comment