Guest krisg Report post Posted February 21, 2011 I am trying to do a loadtest but the load generated is not sufficient to actually put stress on the server because a massive percentage (80% +) of the sessions/requests are erroring with the code 10060. I have checked a few other posts who have had the same problem, and made the changes suggested but this has not fixed the issue. I have attached a log file for one of the users which contains an example of the network error. I am using WAPT Pro 2.1. I do NOT have "keep alive server connection" enabled. My user think time is set at the profile level, and is 15-30 seconds for each user profile. I am NOT testing against a site like Yahoo. Can you please help ASAP. 0_000_0.txt Quote Share this post Link to post Share on other sites
sergei 0 Report post Posted February 22, 2011 It looks like your server is overloaded. Try to use a ramp-up load generation and determine a load level when first errors occur. Quote Share this post Link to post Share on other sites
Guest krisg Report post Posted February 22, 2011 Hi Sergei, We are pretty sure that the server is not being overloaded as the site remains fully usable during the period the load test is running. As well as the site remaining functional and responsive, the CPU utilization on our servers remains quite low, never even coming close to maxing out. Even with significantly lower load levels the errors still occur, albeit at a lower frequency. We actually have 3 load balanced front end webservers to handle the traffic, none of which show CPU utilization above 50-60% during the load test. Quote Share this post Link to post Share on other sites
sergei 0 Report post Posted March 1, 2011 Possibly, the load balancer considers WAPT requests as a DDOS attack, because all requests are sent from the same IPs. Try to disable a DDOS attack filter. Quote Share this post Link to post Share on other sites
