jakarta-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51380] [PATCH] Control reuse of cached SSL Context from iteration to iteration
Date Wed, 15 Jun 2011 16:55:18 GMT

Brent Cromarty <brent.cromarty@yahoo.ca> changed:

           What    |Removed                     |Added
                 CC|                            |brent.cromarty@yahoo.ca

--- Comment #2 from Brent Cromarty <brent.cromarty@yahoo.ca> 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: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org

View raw message