HttpClient4 don't reuse TCP connections

[asfimport]

Maxime Bossard (Bug 60957):
The current implementation of HttpClient4 don't reuse HTTP connections, dispite the "Use Keepalive" checked, the headers are present in the request and in the response.
TCP connections are not closed ether, they quickly move to state TIME-WAIT.

With the same test plan, HttpClient3.1 correctly reuse TCP connections.

Severity: major
OS: Linux

Duplicated by:

• Default values for "httpclient4.validate_after_inactivity" and "httpclient4.time_to_live" which are equal to each other makes validation useless #4266

[asfimport]

@pmouawad (migrated from Bugzilla):
Hello,
Can you test JMeter nightly build ?
http://jmeter.apache.org/nightly.html

This is not a bug but a configuration you have to do on these properties:
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

This bug has been marked as a duplicate of #4266

[asfimport]

Maxime Bossard (migrated from Bugzilla):
(In reply to Philippe Mouawad from comment 1)

Hello,
Can you test JMeter nightly build ?
http://jmeter.apache.org/nightly.html

This is not a bug but a configuration you have to do on these properties:
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

*** This bug has been marked as a duplicate of #4266 ***

Yup, it works with httpclient4.time_to_live greater than the value returned by the server.

I didn't test the nightly build, but I can't see a difference for this property in the 3.2RC2 version of jmeter.properties
cf: https://github.com/apache/jmeter/blob/v3_2_RC2/bin/jmeter.properties