https://bz.apache.org/bugzilla/show_bug.cgi?id=62861

Philippe Mouawad <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |[email protected]
                   |                            |om

--- Comment #1 from Philippe Mouawad <[email protected]> ---
(In reply to Abhishek Rao from comment #0)
> Hi,
> 
> I have a script with 5 http requests which upon executing for 10 iterations
> with keep-alive enabled for all requests, and following are my observations:
> 1. httpclient.reset_state_on_thread_group_iteration=true
> a. With 1000ms think time per iteration
> Expected Output: Connection per iteration
> Actual Output: A total of 10 connections are created, and each connection
> was iteration dependent.
> b. No think time throughout the iteration
> Expected Output: Connection per iteration
> Actual Output: A total of 10 connections are created, and each connection
> was iteration dependent.

This one looks ok, right ?

> 
> 2. httpclient.reset_state_on_thread_group_iteration=false
> a. With 1000ms think time per iteration
> Expected Output: Connection per thread, shared across multiple iterations
> Actual Output: Network inspection shows that 5 connections were created in
> total, with an interval of ~2seconds before the client (JMeter) sent a
> FIN-ACK and closed the connection, which isn't the actual "full" reuse that
> we're looking for with this feature. 
> b. No think time throughout the iteration
> Expected Output: Connection per thread, shared across multiple iterations
> Actual Output: Only one connection was created and used across all the
> iterations.
> 
> It seems though some underlying TCP configuration is being honoured, which
> is causing the client to create a new connection every 2 seconds after ~1+
> seconds of inactivity due to our think time in the script. Is there a way to
> work around this and ensure full reuse of connection? I'm not sure whether
> this is a JMeter bug in the first place.

Have a look at these 3 properties in
http://jmeter.apache.org/usermanual/properties_reference.html:
httpclient4.idletimeout=0
httpclient4.validate_after_inactivity=1700
httpclient4.time_to_live=2000

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to