IIS 5 & IIS 6
"Server too busy" and outbound calls
Last post Jul 25, 2008 08:10 AM by Rovastar
Jul 24, 2008 07:14 PM|theplastictoy|LINK
In a shared hosting environment, one website is making http requests to a web server that, sometimes, isn't available. When this happens, TCP connections for other websites hosted on the same shared server become unavailable (TIME_WAIT). After some time,
the shared hosting server returns "server too busy".
System is Win2k3 , IIS 6
Any suggestions to get around this issue?
Jul 24, 2008 07:25 PM|Rovastar|LINK
Use separate app pools for this problem site and the others on the box.
Check the code to see what is happening. It should exit gracefully and not cause problems.
Get a better understanding of TIME_WAIT and what is happening.
and read articles like this with more suggestions
By default windows 2003 I think has 5000 tcp/ip connections available probably they are all getting used up and server busy appear. If your server doesn't normally get this load I suspect your problem app is spamming out too many connections to the other
server (and no doubt causing that to be not available too) .
You could reduce the TIME_WAIT time before the connection is dropped or increase the TCP connections but that will really only mask the problem.
Kick this problem site off your shared infrastructure. :) First rule of shared infrastructure if one site brings it down get rid of it.
Jul 25, 2008 07:02 AM|theplastictoy|LINK
An urgent thing to do is decrease the Timeout value in the web service proxy class. By default, it's 1m40s.
Also, i believe this server is hosting aprox 20 commercial websites, and some are big ones. Not an optimal solution :(
Each website is on a separate app pool.
Jul 25, 2008 07:03 AM|theplastictoy|LINK
By the way, each site is on a separate app pool.
Jul 25, 2008 08:10 AM|Rovastar|LINK
If you are a hoster common practice is if a shared site adversly effects performance of others then you should remove it.
What does their contract say? Often you can take if you can prove one site is a problem.
In genreal you should look at this policy and review it.