On Saturday, January 30, 2016, sebb <[email protected]> wrote: > On 29 January 2016 at 23:31, Philippe Mouawad > <[email protected] <javascript:;>> wrote: > > Hello, > > I made a real load test today using nightly build and faced an important > > issue. > > > > Here are the details: > > - Test uses 1000 Threads on 1 Instance > > - It uses "Download Embedded Resources" > > - Socket Timeout is set to 10s > > > > There is no overloading of the machine, no impacting GC > > > > Very rapidly, I start getting a lot of errors: > > > > > > - Non HTTP response code: org.apache.http.conn.ConnectTimeoutException > > message:Non HTTP response message: Connect to www.foo.com:80 timed > out > > What is the elapsed time till the timeout occurs?
In the initial test, it happens after 2 minutes at around 300. threads. with a test at 300 threads and a very rapid rampup (5 seconds, with a startup delay of 10 seconds) to reproduce it happens after 16 seconds > > > > > Rate of error varies between 15% and 30%. > > Note that if I navigate on the application, I don't face the errors. > > > > I ran the same test using exactly the same configuration: > > > > - Same machine > > - Same JVM version and tuning > > - Same user.properties > > - Same hc.parameters > > > > But jmeter r1715087 > > And error rate is 0.30%. > > > > > > Note the target server has a load balancer that returns a keep-alive > > duration set to 2 (2 seconds). > > > > This issue is a blocker one for the release of next version. > > I compared code with revision 1715087 and I don't see many changes in > > HTTPHC4Impl that would explain this regression. > > I commented out some suspects , retried but I get same results. > > > > > > I also upgraded to HttpClient 4.5.2 and uncommented the code expected to > be > > added, same results. > > > > So for now I tend to suspect an issue in HttpClient/Core. > > -- > > Regards > > Philippe M. > -- Cordialement. Philippe Mouawad.
