On 23 August 2011 14:23, Milamber <milam...@apache.org> wrote: > Hello, > > I thinks I found a issue with HttpClient 4.1 on JMeter 2.5. > > I've a (big) JMeter test (+800 http requests) on 3 Thread Groups. > TG1 => 63 users > TG2 => 38 users > TG3 => 14 users > > Scheduler test with a duration: 1800 secs (ramp-up : 200 secs, and sync > timer 0.33 sampler/min) > > Platform is a server with Linux 64 bits (debian 6), JDK is 1.7.0 (same > issue with 1.6u27) > (ulimit -n 60000) > > With a HTTP Requests Defaults with HC4 implementation (used by all > requests), after ~650 secs, I've this stats: > > netstat -tuplan > Netstat-hc4 > > grep java Netstat-hc4 |wc -l > 32676 > > grep java Netstat-hc4 |grep ESTA | wc -l > 319 > > grep java Netstat-hc4 |grep TIME_WAIT | wc -l > 0 > grep java Netstat-hc4 |grep CLOSE_WAIT | wc -l > 32356 ===> too big! > > After some time, JMeter shows this errors (and test failed): > java.net.BindException: Adresse deja utilisee (Address already used) > at java.net.PlainSocketImpl.socketBind(Native Method) > at > java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:374) > at java.net.Socket.bind(Socket.java:627) > at > org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:116) > at > org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:148) > at > org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149) > at > org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121) > at > org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:573) > at > org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:425) > at > org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) > at > org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) > at > org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:262) > at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:62) > at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:999) > at > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:985) > at > org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:381) > at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:274) > at java.lang.Thread.run(Thread.java:722) > > > With the same JMeter (same platform), but with a HC3.1 implementation on > HTTP Requests Defaults, the test is successful (no error) > > After ~650 secs, I've this stats: > > netstat -tuplan > Netstat-hc31 > > grep java Netstat-hc31 |wc -l > 628 > > grep java Netstat-hc31 |grep ESTA | wc -l > 108 > > grep java Netstat-hc31 |grep TIME_WAIT | wc -l > 0 > > grep java Netstat-hc31 |grep CLOSE_WAIT | wc -l > 519 ==> good > > I believe is a HTTPClient issue, on close connection? > (http://www.sunmanagers.org/pipermail/summaries/2006-January/007068.html)
I think it's more likely to be that JMeter is not tidying up the HC4 connections properly. Are you using Keep-Alive? Can you reproduce the problem with a simpler test case, e.g. one that could be run against a local server. > > Milamber > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org > For additional commands, e-mail: dev-h...@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: dev-h...@jakarta.apache.org
