Windows Server 2003 SP1 removed the need to set a higher limit for maxconnections.
The number of simultaneous connections in W2K3 SP1 is now limited
only by available system resources or the MaxConnections registry entry.
You *can* set a higher number of connections in an unpatched Windows Server 2003:
Registry path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\HTTP\Parameters
Registry entry
MaxConnections
Value Type
DWORD
Valid data value ranges for this entry are 0 to 4294967295.
Matt, you seem to have a typo :
<add address="*" maxconnection="20"/>
That should be :
<add address="*" maxconnections="20"/>
In any case, if you're running an unpatched W2K3, try setting the registry entry, per the above.
Juan T. Llibre, asp.net MVP
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
======================================
"Aidy" <ai**@noemail.xxxa.comwrote in message news:tO******************************@bt.com...
Someone correct me if I'm wrong, but there is a limit at the TCP/IP layer that means you can only
have two TCP/IP connections to the same machine on the same port at a time. Point IE at a
graphic-heavy site and you'll see it downloads images 2 at a time. As this limit is at the TCP/IP
layer you can't control it from IIS or ASP.
"MattC" <m@m.comwrote in message news:e3**************@TK2MSFTNGP03.phx.gbl...
>I've written an HTTPHandler that implements IHttpAsyncHandler. This handler makes a call to a
webservice that will send back a byte[] to be sent back to the webrowser as an image.
I've set the maxconnections setting on the web.config for the handler and the webservice to:
<system.net>
<connectionManagement>
<add address="*" maxconnection="20"/>
</connectionManagement>
</system.net>
>But when debugging I can see that it is still only making 2 requests at a time. How can I make a
handler that will allow for more than 2 requests at a time.
TIA