https://bz.apache.org/bugzilla/show_bug.cgi?id=62861
Bug ID: 62861
Summary: httpclient.reset_state_on_thread_group_iteration
doesn't reuse connection for think time > 1second
Product: JMeter
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: HTTP
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.1
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.
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.
--
You are receiving this mail because:
You are the assignee for the bug.
