https://bz.apache.org/bugzilla/show_bug.cgi?id=62861
--- Comment #10 from Abhishek Rao <[email protected]> --- (In reply to Philippe Mouawad from comment #9) > Requalifying to enhancement. > > Note there is a relation with this topic: > http://mail-archives.apache.org/mod_mbox/jmeter-dev/201811.mbox/%3CCAH9fUpau- > 3YWao86yU2DhM6mCAwssa61Wqew_iMYtFbmrioRiQ%40mail.gmail.com%3E > > > @Reporter, it would be really nice from you (since I spent time answering > and providing workaround ) to answer comment 3 and confirm provided > information fixed issue 2 and it is now an enhancement request and not a bug. Thought I confirmed in comment#7. Agree that this isn't necessarily a bug and just a behavior of setting TTL at HC level. It looks like we can go with the workaround for now: a. Set TTL to desired value (long enough that connection persists throughout test) on specific jmeter-servers and leave to default for the rest b. Configure run-time thread group enablement as mentioned in comment#5 Thanks for qualifying this as an enhancement. Quick question - will the enhancement be a PoolingHttpClientConnectionManager or httpclient.reset_state_on_thread_group_iteration just made threadgroup local and UI configurable? -- You are receiving this mail because: You are the assignee for the bug.
