How to increase connection limit beyond 40?

Discussion in 'ASP .Net Web Services' started by Homam, Mar 2, 2005.

  1. Homam

    Homam Guest

    I'm having a bottleneck on the maximum number of connections an ASP.NET app
    can call the same web service simultaneously. The maximum number of
    connections is 40, which means the maximum amount of time that a request
    could take is less than or equal to 25ms. But I have some requests that take
    more than that, and this is causing the ASP.NET process to choke on the HTTP
    connections and start throwing errors.

    It seems to me extremely low that you can't practically use the .NET web
    service client on the web tier to communicate with another web service in any
    high volume site.

    Is there anyway to increase the number of simultanous client connections
    beyond 40?
     
    Homam, Mar 2, 2005
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Gordon Beaton

    niotcp 200 connection limit

    Gordon Beaton, Nov 28, 2005, in forum: Java
    Replies:
    2
    Views:
    386
    Gordon Beaton
    Nov 28, 2005
  2. Replies:
    1
    Views:
    1,089
    Victor Bazarov
    Jun 28, 2005
  3. .rhavin grobert

    inc unsigned (whatever) beyond limit.

    .rhavin grobert, Oct 21, 2008, in forum: C++
    Replies:
    9
    Views:
    357
    .rhavin grobert
    Oct 22, 2008
  4. Ed Hardy
    Replies:
    2
    Views:
    173
    Ed Hardy
    Dec 1, 2008
  5. HopfZ
    Replies:
    1
    Views:
    124
    web.dev
    Aug 17, 2006
Loading...

Share This Page