jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 60768] Jmeter: testing with TLS cert creates new connection with every request
Date Thu, 23 Feb 2017 13:20:38 GMT

UbikLoadPack support <> changed:

           What    |Removed                     |Added
             Status|NEW                         |NEEDINFO

--- Comment #1 from UbikLoadPack support <> ---
(In reply to digant from comment #0)
> Hi,
> When I use Jmeter with TLS client cert, it creates a new connection for
> every request, though I have keep alive on.
> When I tried to test the same it Apache httpClient directly, I noticed that
> we need to have one special setting in httpclinet configuration 
> ".setUserTokenHandler(new NoopUserTokenHandler())", 

Are you sure NoopUserTokenHandler does what you think ?
IMO, it does exactly the contrary which is to return a null state.

Can you give more details on:
- your test plan ? Cookie Manager , pause times between request ? 
- What makes you think a new connection is created for every request ?

If you're using 3.1, did you modify properties:

Which controls lifetime of connections ?
I would suggest you increase for example this one to a higher value  :

There is also a known issue where httpclient4.time_to_live does not correclty
validate connection, could you in this case download nightly build and check:


> in order to make httpclinet use the same connection. 
> I was wondering if there is there any way to override httpClient
> configuration in Jmeter?
> I tried to used Jmeter 2.13 and Jmeter 3.0 and found the same issue with
> both.
> Please suggest.

You are receiving this mail because:
You are the assignee for the bug.
View raw message