On 23/08/07, Christiaan Lamprecht <[EMAIL PROTECTED]> wrote: > On 8/22/07, sebb <[EMAIL PROTECTED]> wrote: > > JMeter does not do any SSL, other than configuring the connection, so > > any renegotiation is done by the SSL provider, i.e. by default JSSE in > > Java 1.4. > > Thanks for the quick reply. Sounds like good news. > > > > There are a few things which can affect how JMeter responds to this: > > > * Does the simulated JMeter client wait for a reply? and will it > > > respond to a renegotiation request instead? > > > * Is there any SSL state shared between the clients/threads/etc... > > > during the simulation > > > * If renegotiation occurs, will JMeter incorporate the renegotiation > > > time into the response time for that request? > > FYI, anyone who's interested: > * I think it's safe to assume the simulated client waits for a reply. > * Seems then that the SSL state will also not be shared; see paragraph > 2 under 4.1 http://jakarta.apache.org/jmeter/usermanual/test_plan.html
Except ... This was true for all but the SSL context, which was shared between threads in 2.2 and earlier. Version 2.3RC3 changed the SSL context to be per-thread; however there was a bug that meant some of the objects were recreated too often. This has been fixed in the current nightly build. > * Guess I'll have to wait and see > > Will try to update this when I'm done if anyone's interested > > Thanks again > Christiaan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
