IIS 7 & IIS 8
Pages appear to stop responding
Last post Mar 27, 2013 03:03 PM by jmch
Mar 04, 2009 03:21 PM|LINK
We're running IIS7 on WS08. I have experienced SEVERAL times when I'm accessing a page on this server where it will simply stop responding. The load progress bar will show no progress at all, and after a minute or two, I finally stop it. I can either
refresh the browser (which usually immediately brings the page up), or go directly to the page or a different page on the same web site. I have seen this happen on standard html pages as well as asp and asp.net (2.x) pages. It happens most of the time on
pages that I've just changed, but I've seen it happen on pages that I have not changed in quite a while.
I have checked the event log when this happens, and there are no entries in there indicating any errors of any kind.
I usually access this server across the network, so instead of a standard "www.mysite.com", I usually do a "http://myserver/myfolder/mypage.htm" sort of thing. But, I believe I've seen this problem when accessing it both ways.
We have some of the same apps running on a WS03 server perfectly.
1) Any idea what is causing this?
2) If there are no ideas, are there any testing methods anyone can suggest to help me figure this out?
Mar 04, 2009 05:03 PM|LINK
Use failed request tracing - it should pinpoint where the request processing is getting stalled.
Mar 04, 2009 06:48 PM|LINK
Thanks, I've just enabled that. I've set it to log situations where it takes longer than 2 minutes to respond to a request. I'll check the log when I run into it again (after waiting 2 minutes, of course), and see what I get.
Mar 10, 2009 02:19 PM|LINK
OK. I've "got one on the line". I have Failed Request Tracing turned on, and I've set it to a time limit of 2 minutes. Here's the problem. 2 minutes came and went. It did not respond, nor did it fail. However, after more than 5 minutes,it finally responded
and displayed the screen as it should have. There were no errors or anything, just an incredibly long delay before it displayed the correct screen. There is nothing in the Failed Request Log (I suppose, because it didn't fail).
Any ideas how I can figure out why this thing took 5 minutes to respond when it should have taken only a second or two at the most?
Mar 10, 2009 04:57 PM|LINK
What does the time taken field in IIS log say - can you get failed request trace if you remove the "2 minutes" condition just add a condition for all status-codes "200-999".
Mar 10, 2009 05:21 PM|LINK
Here is the first entry from the log that accesses the page that had a long delay:
2009-03-10 14:22:03 192.168.1.8 GET /dlg/tsanat/HSMSConfPayment.aspx - 80 - 192.168.1.105 Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-US;+rv:220.127.116.11)+Gecko/2009021910+Firefox/3.0.7 200 0 0 1716
Don't know how to read this log entry, but the number at the end (which could be the time??) can't be seconds, and I wouldn't think it would be mili-seconds either. It was just a little over 5 minutes, and that doesn't match with this.
Mar 10, 2009 06:52 PM|LINK
I have encountered the same issue and believe it is specific to recent versions of FireFox (3.0.6+) and IIS7-hosted websites. I posted the following on a FireFox board, but didn't garner much response:
I believe there is some issue with the way FireFox and IIS7 interact with regard to connection handling. Failed request tracing is not much help in this situation as it only lists that the request has "NO_END" in the BEGIN_REQUEST stage of processing.
The issue appears to be intermittent (at least for me) but it happens frequently enough to cause user problems and complaints. I have no idea where to go next to resolve this problem and hope that MS will help figure out what the root cause of this issue
Mar 10, 2009 09:19 PM|LINK
That is in milliseconds - so 1.7sec - can you collect a netmon trace when the problem happens. Also, to be sure, you are running a server sku of IIS - the client skus (vista) have limits on number of concurrent connections so you may have requests getting
queued while earlier requests are being processed.
Mar 10, 2009 09:35 PM|LINK
I can tell you that the request took a lot longer than 1.7 seconds to process. I timed it, and while I didn't get the exact second that it stopped, I know it was more than 5 minutes. So, that being the case, maybe IIS responded but for some reason the
browser didn't pick up on it? It sounds a lot more like the fellow might be correct about it being an issue with IIS7 and Fire Fox (and maybe IE7?) not talking with each other? This is an IIS7 issue, because this app works fine with IIS6.
How do I run a "netmon trace"?
What do you mean by "running a server sku of IIS"?
As far as concurrent connections, I seriously doubt that I had very many people connected at the time. I do run several web sites on the machine, but it's use mainly for development. If I had to guess, there may have been 6 or 7 people connected at the
most.Plus, I can be almost 100% sure that no one was accessing this particular application at the time, because this was a development folder that no one accesses but me (except rarely someone else would, but most likely not today).
Mar 10, 2009 09:42 PM|LINK
I mean you are running on windows server 2008 and not vista.