https://issues.apache.org/bugzilla/show_bug.cgi?id=55023
--- Comment #1 from Sebb <[email protected]> --- Thanks for the report and analysis. Each HTTP sampler has its own HttpSamplerBase instance, so provided that the protocol is a fixed string, the check you propose is fine. For a dynamic protocol it might depend how the protocol was defined - perhaps the value might not be correctly defined at test iteration start [would need checking]. However as you further point out, the HC3/HC4 implementations clear all current connections in the overridden notifySSLContextWasReset() methods. I assume this is because the context is bound to the connection somehow. Ideally one would like to only clear the relevant entry(s). This would be tricky to do at test iteration start, since the connection map key might rely on dynamic values. So a possible solution might be to set a flag in the testIterationStart() method if the context is to be reset. The first sample that uses SSL would then ignore any cached connection, and always recreate it. And then clear the flag. I think this should solve both issues. -- You are receiving this mail because: You are the assignee for the bug.
