https://bz.apache.org/bugzilla/show_bug.cgi?id=63110
Philippe Mouawad <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- OS| |All --- Comment #10 from Philippe Mouawad <[email protected]> --- (In reply to david.imlit from comment #9) > Hi, > > I can confirm the this bug is still active in 5.1. > Worked fine in 4.0 > > I resolved it by adding this line to the user.properties file. > httpclient.reset_state_on_thread_group_iteration=false > > Is this correct? Seems like a bad experience if keep-alive does not by > default. If you read previous comment, you'll see that it's not that straightforward. We have integration tests for this feature which show it works. Do you have a reproducible case showing issue ? Be aware that Keep-Alive will not persist accross iterations since by default JMeter considers a new iteration is a new user. When you set: httpclient.reset_state_on_thread_group_iteration=false you say "New thread iteration is not a new user". Do you confirm it's your case ? I think in the future we should make this an option of Thread Group (consider new iteration as new user: true/false) and impact as a consequence: - This setting - Cookie Manager - Cache Manager Thanks -- You are receiving this mail because: You are the assignee for the bug.
