I'm having an issue with a migration to IIS 7.0. In the previous version of IIS I have been able to set the Application Pool queueLength to 0 to set it to 'unlimited' but in IIS 7.0 the max it will let me set it to is 64K.
It is recommended that you set this value to 1.5 times the number of concurrent connections otherwise you might get a 503 error.
I am running upwards of 130,000 concurrent connections on this system and it seems the 64K limit is just too low. How do I go about getting all these connections connected at once without suffering any 503 errors.
We have a DefaultAppPool and then my ClientApplicationPool that I created.
If there is anymore info needed please let me know.