Aha! I figured out where I was going wrong. I had been setting https.use.cached.ssl.context to false and using HTTPClient 4, but my test written in such a way so that the property never had a chance to reset the SSL context. My test was using an infinite loop with a counter + Test action sampler to exit after 1000 requests, and the https.use.cached.ssl.context property acted on the iteration of the thread group, not the inner loop. When I changed my test to have the thread group infinitely loop (which is actually simpler yet with the same functionalilty) with the same exit action, the SSL context is reset and each HTTPS request is using a new SSL session id!
Thanks for pointing me in the right direction Philippe! Kaelen Proctor -----Original Message----- From: Philippe Mouawad [mailto:[email protected]] Sent: July-31-13 2:15 AM To: JMeter Users List Subject: Re: Is it possible to force JMeter to use a new SSL session ID for every HTTPS request? Hello, This should work: https.use.cached.ssl.context=false is set in user.properties use either HTTPClient 3.1 or 4 implementations for HTTP Request If it doesn't you should report a bug. Regards Philippe @philmdot On Wednesday, July 31, 2013, Kaelen Proctor wrote: > > I am trying to benchmark SSL handshakes per second with JMeter and I > am trying to see the performance difference between HTTPS requests > with and without SSL session reuse. However I seem to be running into > the wall with JMeter as I cannot determine how to have every HTTPS > request use a brand new SSL session id. As I've come to understand > from Googling on this topic, Java by default has an unlimited SSL > session cache in which entries expire after 24 hours. > > I've tried using the JMeter properties "https.use.cached.ssl.context" > and "https.sessioncontext.shared", but even together they don't cause > new SSL session ids to be used for each request. From playing around, > at best if I have 10 threads making 5 HTTPS requests, the first 10 > requests will have new SSL session ids, but the remaining 40 will > reuse SSL sessions. I've verified this behaviour with both ssldump > (seeing the resumed SSL session > ids) and in my STunnel logs (when STunnel logs a previous session is > reused). > > Even setting the Java property "javax.net.ssl.sessionCacheSize" to 1 > does not seem to work, I'm guessing it must get applied per thread. > > So I was wondering if it possible through JMeter (or Java) to have > every HTTPS request use a new SSL session id? > > Kaelen Proctor > > > Confidentiality: The information contained in this e-mail and any > attachments are confidential. If you are not the intended recipient, > you may not copy or distribute this information. If you have received > this communication in error, please notify the sender immediately and > delete it from your system. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > <javascript:;> For additional commands, e-mail: > [email protected]<javascript:;> > > -- Cordialement. Philippe Mouawad. Confidentiality: The information contained in this e-mail and any attachments are confidential. If you are not the intended recipient, you may not copy or distribute this information. If you have received this communication in error, please notify the sender immediately and delete it from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
