Quantcast
Viewing all articles
Browse latest Browse all 27852

Server too busy warning while servers arent't busy at all...

Last week we updated our (cluster) hosting environment to Windows Server 2012 and IIS8. Since the update we experiencing some "server too busy" warnings onaspx-sites (asp.net).

We have multiple load balances (hardware) webservers with 24GB memory and XEON processors each. De servers arenot(physical) busy at all during the warnings... All the servers in our cluster arenot using more then 10GB physical memory. Also the virtual memory on the servers isn't higher then 8GB each (pagefile is 27.2GB).

Here’s what we figured out so far. When we set the “Virtual Memory Limit” to zero in the “Application Pool Defaults”, the servers will work for a couple of minutes. But after some minutes, suddenly all (or some) asp.net websites are giving a “server to busy” warning. When we refresh the sites, sometimes they work and sometimes they don’t. Websites using php, html, etc aren't effected with "server too busy" warnings at all.

We are now using  the following “Application Pool Defaults” to let the asp.net sites "work". However, some asp.net sites are not working properly with these settings at all. *

Private Memory Limit: 100mb
Virtual Memory Limit: 100mb

* A worker process with process id of 'x' serving application pool 'domain' has requested a recycle because it reached its virtual memory limit.

Can someone tell us what we doing wrong? Why are the asp.net sites giving a “server to busy” warning while the servers aren’t busy at all? It's probably a setting that we forget... The "ApplicationHost.config" is taken from IIS7 with of course somerequired adjustments.

Thanks in advance, if you need any more information about settings etc please let us know.


Viewing all articles
Browse latest Browse all 27852

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>