IIS 7 & IIS 8
Pages appear to stop responding
Last post Mar 27, 2013 03:03 PM by jmch
Mar 10, 2009 11:48 PM|LINK
OK. downloaded and installed. I guess I'll wait for the next problem and then run netmon.
Yes, I'm runing WS08, not Vista.
Mar 10, 2009 11:57 PM|LINK
Btw, to use netmon, you will need to browse from an external machine - netmon cannot capture traffic over localhost.
Mar 11, 2009 12:03 AM|LINK
Will browsing from a different machine on the same network work? I usually do http://mymachine/myapp/mypage.aspx (for instance).
Mar 11, 2009 02:22 PM|LINK
OK. Assuming that browsing to the server from another machine on the network is OK...
I had it happen again. I then ran netmon and let it run for an entire 10 minutes. It never did respond, and I got tired of waiting, so I hit the browser stop button to stop it. However, I did save the captured netmon output. What should I be looking for?
Personally, I'm thinking that whatever the problem was that caused it had already occurred by the time I started netmon.Because by the time I notice that it's not responding, I'm thinking the problem has already occurred and it's already too late to start
netmon. At any rate, if there's something here that I should look for, let me know what it is.
Mar 12, 2009 02:33 PM|LINK
Anil, if you are looking for an example you can see it by downloading FireFox and browsing to our corporate website:
www.winebid.com. Click the Search button to get a listing of results. You'll notice that the page comes back very quickly. You can click next/prev links to navigate quickly between subsequent search result pages. However,
if you stop on a particular page and wait over 60 seconds, and then click the prev or next link FireFox will hang as described. It doesn't happen all the time, but most of the time under these circumstances. The pages do eventually respond... but only after
minutes of nothing but a spinning progress indicator.
Because the problem (at least in our circumstance) happens only after some period of inactivity, it leads me to believe that it has to do with how IIS7/FireFox handle the connection. Could IIS7 be timing out a connection that FireFox thinks is still open
for use? I know nothing of the inner workings of either so that is just a guess based on observations. The problem is clearly reproducable though, and does not happen with Internet Explorer or Safari... only FireFox and only recent builds.
Mar 12, 2009 05:18 PM|LINK
Can you zip up the cap file and e-mail it to me at anil (dot) ruia (at) microsoft (dot) com?
Mar 12, 2009 06:22 PM|LINK
There could be many issues why a page takes a long time to load. Network issues, firewall, route, etc misconfiguration, code, etc
As anil suggests maybe a network trace is the only way to work out more of what is occurring
I can reproduce your problem. Often it is like 10-30 seconds not minutes to display teh page in FF3.0.7
You need to find a pattern where it is reproducable.
What do the IIS logs say? Remember the time field is the time written to the logs when finished to get the start time it is time-timetaken.
What does the application trace routing reveal? Is it the first request that takes the time or sending the last one back or spread throughout the process.
Look at the release notes for firefox when you first had a problem http://www.mozilla-europe.org/en/firefox/3.0.6/releasenotes/ and https://bugzilla.mozilla.org/buglist.cgi?keywords_type=anywords&keywords=fixed188.8.131.52+verified184.108.40.206 anything relevant there?
Mar 12, 2009 06:44 PM|LINK
The delay's I'm experiencing last much more than 10-30 seconds. I waited 5 minutes one time before it responded, and another time I waited 10 minutes before just hitting the stop button. The thing about this is when I stop it, I can usually hit the refresh
button, click the link again, and it pops up in a split second. So, it's not a coding issue, or a database problem. When this happens and I stop/refresh/click again, it pops up immediately. And, there is practically no traffic on the server, so I know the
server is not the issue either.
The IIS logs don't help much. They only say that a page was accessed at a certain time, and as pointed out in a previous entry here, they showed a response time of 1.7 seconds, but that response did not show up in my browser that fast. This server is used
for development, and when I upload the same code to our WS03 live server, it works perfectly, and I experience no such delays.
If I understand what you are asking about application tracing, you have to implement that when you're experiencing the problem, don't you (or before?). Thing is, as some one else already pointed out, this doesn't happen all the time. In fact, I find that
most of the time it works just fine. However, if I let it sit for a little while, then try, sometimes I'll get the long delay, sometimes I will not.
I checked the Fire Fox logs as you indicated, and didn't see anything obvious there.
Personally, I believe this is an issue in IIS7 / WS08 as WS03 is working fine. It could be a configuration issue, but I really don't know what sort of configuration changes to make.
Mar 12, 2009 06:57 PM|LINK
BTW most of my above reply was aimed at ianderson. I see these as different issues not the same one.
Often when I have seen similar issue you get a http 200 status and win32 error of 64. Which often means a network issue so check this.
Yes, you will need to run traces before an issue occurs so it can catch the error. So you will need to do this for netmon too it will be useless without and note the times when the delay is occurring.
These sorts of problems are often the most difficult to resolve (any version of IIS) as there are so many factors to consider and there is no 100% reproducable behaviour.
But does it ever occur internally (ideal test is on the box itself)? or it is all external traffic.
You need to check all the routing/firewall/etc stuff too. I have seen many times that they can cause issues like this.
Also don't use different OS's for dev/staging and production it will just lead to more problems in the long run as you are not testing the site in the correct enviornment.
Mar 12, 2009 07:18 PM|LINK
My problem and ianderson's seemed to be the same issue to me, but not sure. I thought that's why he chimed in.
Problem is that I'd have to be running traces all the time as the problem is intermittent. I think last time Anil tried to help me set up one of these traces, you have to set it up on a certain process. I'll try to reproduce it by delaying on a page for
a while, then clicking to see if there's something there causing the problem.
I guess you could say it's occurring internally. As stated earlier, I'm not going to http://www.whatever..., I'm going to http://myserver/mypath/myapp.aspx. So, yes, I'm on an internal network. This is going through the firewall, but I'm not sure what
sort of issues to look for. It would seem to me that if it were a firewall issue, then it would delay or fail all the time.
The way things are going, I probably won't be developing on different OS's for long. I think we are planning on purchasing a copy of WS03 and re-formatting this server to get rid of WS08. I have several other problems too that only seem to be occurring
in WS08 that are working fine in WS03. Problem is that WS03 isn't going to be around forever, so I need to find out what the problem is and get it fixed now instead of just delaying it.