Re: CAtlHttpClient Navigate()

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



You seem to be under the impression it is trivial to create 4000 threads without causing problems in your test program. Remember every thread is assigned its own stack (default 1MB). Since every Win32 process has a 2GB virtual address space, you are going to run into serious problems once you exceed 2000 threads (memory thrashing).

I suggest that the problem isn't in CAtlHttpClient, but more likely in the way your test harness is designed.

Brian




"Jaya" <Jaya@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7E8A3D00-17D8-43E7-8A19-5E80436388F6@xxxxxxxxxxxxxxxx

4000 simultaneous requests (threads). We don't see any unsual spikes with
memory or CPU. After about 4000 requests we start getting a "WSAEADDRINUSE"
error code back.

the CAtlHttpClient::Navigate() is being called from within an ISAPI filter
and is making a remote HTTP request to a tomcat servlet. We verigfied we were
successfully able to make > 10000 simulateneous requests to the tomcat
service if we hit it directly.

do we need to call CAtlHttpClient::Close() explicitly?

If I need to provide more information, please let me know.

"Brian Muth" wrote:

4000 requests one at a time or 4000 requests at once? How are you setting up your test harness? Do you create 4000 threads, or
launch 4000 processes? If serially, are you watching for memory or resource leaks?

There is a lot of missing information in your post.

Brian

"Jaya" <Jaya@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:12C40501-67F6-4E8F-95E3-D9E03BC780A7@xxxxxxxxxxxxxxxx
> Hi
>
> We are using VC8 and the CAtlHttpClient to make HTTP requests to a remote
> server. We were observing in our load test environment that after about 4000
> requests CAtlHttpClient::Navigate() starts failing and none of the requests
> after that are successful.
>
> I was wondering if CAtlHttpClient has a limit on the number of socket
> connections ?
>
> We have verified the tomcat service on the remote server is not erroring out
> and can handle over 100,000 requests easily when they are not originating
> from CAtlHttpClient.



.



Relevant Pages

  • Re: CAtlHttpClient Navigate()
    ... TCPWaitedTimeDelay registry setting parameter to control the number of ... of 4000 sockets and that was the point when we started seeing the Socket ... I suggest that the problem isn't in CAtlHttpClient, but more likely in the way your test harness is designed. ... After about 4000 requests we start getting a "WSAEADDRINUSE" ...
    (microsoft.public.vc.atl)
  • Re: CAtlHttpClient Navigate()
    ... 4000 requests one at a time or 4000 requests at once? ... How are you setting up your test harness? ... We are using VC8 and the CAtlHttpClient to make HTTP requests to a remote ... We have verified the tomcat service on the remote server is not erroring out ...
    (microsoft.public.vc.atl)
  • Re: [Full-disclosure] Netgear DG632 Router Remote DoS Vulnerability
    ... think that only GET requests are CSRFable! ... Netgear DG632 Router Remote DoS Vulnerability ... TN> on that LAN and the "remote management" interface is ...
    (Full-Disclosure)
  • Re: Fao Ken Kolda
    ... This is the remote obj that is in an empty web project ... enable custom error messages, "Off" to disable. ... access must be disabled in IIS. ... which requests belong to a particular session. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: [Full-disclosure] Netgear DG632 Router Remote DoS Vulnerability
    ... Netgear DG632 Router Remote DoS Vulnerability ... TN> to crash and stop responding to further requests. ...
    (Full-Disclosure)