There is 'Connection Throttling' and "Request Throttling' (which ATS doesn't have). If the web server has something like keep alive enabled or connections are still live, even though something is throttled, doesn't mean that the HTTP 'requests' are still not overwhelming the server. Well also for that matter that the TCP stack is configured to handle '70000/31500' connections as you've configured it.
Try setting keep-alive lower, on TCP and in ATS and see if that kills the connections faster so that you can make a HTTP connection/request. Talin Senner Wildcard Corp. http://cdig.me - http://www.wildcardcorp.com Secure Web CMS Hosting - CDN - DNS - IPv6 Security.Technology.Solutions *We do it all for you* On Tue, Nov 13, 2012 at 12:08 PM, David Carlin <[email protected]>wrote: > I have the following config: > > proxy.config.net.connections_throttle = 70000 (in records.config) > proxy.config.net.throttle_enabled = 1 (ATS default, not specified in > records.config) > > The docs say ATS should start throttling when client connections reach > 31500 with the config above (90% of half of the value > of proxy.config.net.connections_throttle). > > The problem I'm having is that sometimes once throttling occurs, the > server never recovers. I cannot connect to ATS via HTTP after a throttling > event, even long after traffic has died down. Has anyone else ever > experienced this? >
