URGENT Web service failing...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am working on web service which in turn call com components. if # of users
using the web service increases. Web service fails is there some why I can
prevent max # of concurrent users using the web service.

Thanks
Ajit
 
the default webservice connection limit is 2, you just need to bump that up
in the config files

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
 
It is per user right ...
Anyhow I want to set web service so that not more than 4 users are
concurrently connected to the service.

Thanks
Ajit

Alvin Bruney - ASP.NET MVP said:
the default webservice connection limit is 2, you just need to bump that up
in the config files

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------



ajit said:
I am working on web service which in turn call com components. if # of users
using the web service increases. Web service fails is there some why I can
prevent max # of concurrent users using the web service.

Thanks
Ajit
Click to expand...
Click to expand...
 
Is this what you are looking for:

From MSDN:
maxconnections
The default two-connection limit for connecting to a Web resource can be
controlled via a configuration element called connectionManagement. The
connectionManagement setting allows you to add the names of sites where you
want a connection limit that is different than the default. The following
can be added to a typical Web.config file to increase the default value for
all servers you are connecting, to a connection limit of 40.

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

<system.web>
...It should be noted that there is never a limit to the number of
connections to your local machine, so if you are connecting to localhost,
this setting has no effect

or is it this: http://blogs.msdn.com/darrenj/archive/2005/03/07/386655.aspx
 
Back
Top