On Oct 25, 12:36 pm, Banks1850 <sh....RemoveThis@ebsystems.net> wrote:
> We have a production website that runs some asp pages that are housed
> on a shared DAS drive that multiple IIS servers access, they are load
> balanced via a level 2 switch. 1 of the servers is W2K sp4 with IIS
> 5, the other two servers are W2K3 with IIS 6. All three serve the
> pages correctly but randomly (about once or twice a day) the two IIS 6
> machines time out. We have a test asp page that is called every 2
> minutes for all three machines to check for connectivity.
> The details are that the web servers all have the exact same setup,
> multiple virtual directories and pages, the two W2K3 machines don't
> time out at the same time, and they always are right back up 10
> seconds later like they never skipped a beat. The web logs only
> mention that the time taken is about 4 to 5 times as long (about 10000
> to 20000 Milliseconds) as a normal request takes. Since this doesn't
> happen on the IIS 5 box, I doubt it's a network issue, and since it's
> random, I don't think it's a permissions issue. Any information you
> may have would be great.
Are you using WS03 RTM or WS03 Service Pack # installed.
Is this a client-side or server-side timeout. If you say that web logs
say time-taken is about 4 to 5 times as long as a normal request, then
the timeout is due to the client and there's nothing you can do other
than figure out why the time-taken is 4 to 5 times as long.
How long is the connection timeout set on your application that is
pinging ASP?
What exact code is run in this test ASP page?
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//