You need to disconnect the session once the work is done and restart it again.
Connect > do your work here > disconnect completely from server and then again connect to the server. It seems to be that you are disconnecting from the server. Are you able to do this correctly with 1 thread ?. The last time I did benchmark for SSL , it took close to 80 ms for handshake for NYC network bandwidth and it was 2 way ssl handshake. ________________________________ From: Kaelen Proctor <[email protected]> To: "[email protected]" <[email protected]> Sent: Tuesday, July 30, 2013 10:49 PM Subject: Is it possible to force JMeter to use a new SSL session ID for every HTTPS request? 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] For additional commands, e-mail: [email protected]
