Discussion Locked

40 User Limit Problem in IIS

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have recently begun stress testing our web site and noticed that as soon as we attempt 41 concurrent connections against IIS 4.0, many of the requests are not responded to by the server. We are not invoking an .ASP page, only a simple "Hello World" .HTML file. This same behavior occurs on multiple boxes, each a dual processor system. 0 - 40 works fine. 41 is the magic number where things fall apart. I've tried various metabase and registry setting all to no effect. Have installed Apacheand don't have this problem so I don't think it's network infrastructure related. If calling an ASP page, an HTTP 500 error is returned to many of the connections opened by the load test tool. HTTP Result Code not returned is the error returned when using ASP or HTML files as the target of the load test with > 40 users.

3 replies

by dle

Start the IIS Management Console. Take a look under the Website's properties - Web Site tab. Is there a limitation on number of connnections? Change it to Unlimited or a higher number.

by brian.swanson

No, there is no limit on connections. FYI, I am not getting the error while using an internal IP address to access HTML-only pages. It is only when using an external IP address that goes through our proxy server that this problem occurs. But 40 also seems to be a magic number even with the internal IP address for ASP. Instead of getting an ASP error though, the entire site just seems to hang. I can't even restart the service -- the box needs to be restarted...

This discussion is closed to new replies.