https://bz.apache.org/bugzilla/show_bug.cgi?id=62861
--- Comment #4 from Abhishek Rao <[email protected]> --- (In reply to Philippe Mouawad from comment #3) > (In reply to Abhishek Rao from comment #2) > > Hi Philippe, > > > > The first one is okay. > > > > The configuration you mentioned works, but how do I achieve pooling and > > indefinite reuse rather than reusing for an arbitrary time period? For > > example: I have scripts acting as clients using pooled connection > > architectures to talk to web-services internally where this feature will be > > really useful in simulating. > > What if you set: > httpclient4.idletimeout=0 > httpclient4.validate_after_inactivity=1700 > httpclient4.time_to_live=Very high value > > > > Can this be a UI modifiable in future and > > parametric? > > Also, how do I achieve hybrid simulations with one thread group using > > httpclient.reset_state_on_thread_group_iteration=true and one that needs it > > set to false? > > This would be an enhancement request. > Workaround is to use distributed testing with 1 JVM in first mode and second > JVM in second mode. I dont think the workaround would apply for my scenario, because there's two thread groups in the same script and each requires a different setting. Distributed mode with different settings across JVMs would mean both the thread groups are affected, when the scenario calls for just one thread group to have the setting reflected. I think I'll split it into two tests for now and run them in parallel. I think the aforementioned will make for a great enhancement, I also found out that HC4 supports PooledConnectionManager which solves the problem. -- You are receiving this mail because: You are the assignee for the bug.
