Calling web service from web page; concurrency problems?

  • Thread starter Thread starter tale
  • Start date Start date
T

tale

Hello all,

I really need an answer to this post, so I'm trying to repost it. My
question is below. I've included all of the original posts below.

Here is my questions to the last response.
actually this limit applys to asp.net. the default behavior for asp.net page
making webservice calls is still two connections per server. you
canoverride this limit at runtime.
Click to expand...

Ok, so this does apply to asp.net.
the reason for the limit is net etiquette. one client is not supposed to
overuse a remote resource. in this case your web server is the client, but
the rule is same, you should not overload a remote server unless you know
its ok, so the override should be on a server by server basis.
Click to expand...


So does this 2 connection limit apply to each page, the web site
(assuming you are running multiple sites on one server) or the server
itself?

If it applies to the server, then I have another question. In my
first post, I stated that I thought passport used web services. How
can this limit apply to the server and these web sites that use
passport still handle the amount of concurrent page view thst they
normally handle?

-- Tale




Here are the original post and responses:


actually this limit applys to asp.net. the default behavior for
asp.net page
making webservice calls is still two connections per server. you
canoverride this limit at runtime.

the reason for the limit is net etiquette. one client is not supposed
to
overuse a remote resource. in this case your web server is the client,
but
the rule is same, you should not overload a remote server unless you
know
its ok, so the override should be on a server by server basis.

-- bruce (sqlwork.com)
 
with wininet the default is 2 (active) connections is per server to the same
remote server. with .net I'm not sure if its per server or app domain (I
would hope its per server).

In the case of Passport, MS probably permits more than 2 connections per
server, so sites calling Passport, just have to up the connection limit.

If you call your own websevices, these are good candidates to increase the
connection limit count above 2, or you may see scaling issues.

-- bruce (sqlwork.com)
 
actually this limit applys to asp.net. the default behavior for
asp.net page
making webservice calls is still two connections per server. you
canoverride this limit at runtime.
Click to expand...

Ok, I'm running into exactly the same problem. I have an asp.net web
page that uses a .net proxy class to connect to a web service and
retrieve info. For what it's worth, the web service is running on a
Tomcat server on a seperate machine.

I really need to pound this thing from the client end to see if the
connection pool I've built is functioning properly.

So, how does one override the 2 connection limit in .net? There's
surprisingly little info on this.

Thanks for the help.
 
Modify the connectionManagement element in machine.config (machine wide) or
web.config (per application):

<system.net>
<connectionManagement>
<add address="*" maxconnection="6"/>
</connectionManagement>
</system.net>


This would allow for 6 concurrent outbound calls.

Btw the default limit of 2 is imposed by the HTTP 1.1 standard. This limit
makes sense when the client is a desktop application, but not really when it
is a web application.

hth, Sami
www.capehill.net
 
Back
Top