https://issues.apache.org/bugzilla/show_bug.cgi?id=51380
Brent Cromarty <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Brent Cromarty <[email protected]> 2011-06-15 16:55:18 UTC --- Currently the HTTPClient sampler creates an SSL context and connection (i.e.: full handshake) for each thread on the first iteration only. Subsequent iterations reuse their cached SSL Context thereby reusing an existing SSL handshake. While this is typical of the way that a browser behaves (caching and reusing an SSL context where possible) it limits our ability to do specific testing of how a system will handle a constant load of N users when having to perform SSL transactions. The patch I have proposed adds a new property "https.use.cached.ssl.context" to the jmeter.properties file. The default value is "true" to preserve existing functionality. If false the override of public void testIterationStart(LoopIterationEvent event) will get the SSL manager instance and call the resetContext() method, nulling the current threadLocal SSL context, and closing any currently open connections in the HTTP Client. This allows us to create a new SSL context/connection each iteration, but reuse that context within the iteration. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
