Hello, This is not a bug but a configuration you have to do on these properties as JMeter cannot guess your particular ones: Those are the defaults
- httpclient4.idletimeout=0 - httpclient4.validate_after_inactivity=1700 - httpclient4.time_to_live=2000 Read : http://jmeter.apache.org/usermanual/properties_reference.html Default values have been improved in 3.2 Regards @UbikLoadPack On Wed, Apr 26, 2017 at 5:22 PM, Ken Cox <[email protected]> wrote: > In JMeter 3.2, the HttpClient3.1 implementation was removed, and for > me, Use KeepAlive stopped working. That is, the connections are not > reused. > > With JMeter 3.1 I was using HttpClient3.1, and the number of TCP > streams opened by JMeter was exactly the number of threads. With > HttpClient4, JMeter closes the connection after 2 or sometimes 3 > requests. (I see the FIN coming from the client). The same thing was > true of HttpClient4 in JMeter-3.1 as well. > > Is there something I can do to cause HttpClient4 to keep the connection > open? > > I did not find any bug reports that matched. I am willing to file one > with test data if we determine it's worthwhile. > > Environment: > * CentOS 7.3.1611 > * openjdk version "1.8.0_121" > * JMeter-3.2 > > Thanks, > -- > Ken > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Regards Ubik Load Pack <http://ubikloadpack.com> Team Follow us on Twitter <http://twitter.com/ubikloadpack> Cordialement L'équipe Ubik Load Pack <http://ubikloadpack.com> Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
