Hi Rainer, I think I fixed with Revision: 1721771 the bug https://bz.apache.org/bugzilla/show_bug.cgi?id=57804. Could you have a look and test.
Beside this, I notice a change in the logs in the NoClientCert test case attached between 2.13 and 2.14, I cannot tell if it's a bug or regular. If you compare nohup-2.14-pre-commit-1721771-no-client-cert.log with nohup-2.13-no-client-cert.log. With 2.13 I see only 1 time => *** ClientHello, TLSv1 With 2.14 I see 4 times => *** ClientHello, TLSv1, but preceded the 3 last times with => %% Try resuming [Session-1, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA] from port 2571 Regards Philippe M. @philmdot On Fri, Dec 18, 2015 at 12:27 AM, Philippe Mouawad < philippe.moua...@gmail.com> wrote: > Hi Rainer, > Why not ask on httpclient user mailing list? > Regards > > > On Thursday, December 10, 2015, Rainer Jung <rainer.j...@kippdata.de> > wrote: > >> Am 09.12.2015 um 23:17 schrieb Philippe Mouawad: >> >>> Hello, >>> We have a quite rich version now I think (more than 50 >>> bugs/enhancements+ 2 >>> major features) , what about releasing a new version ? >>> >> >> I ran into 57804 which is unfixed. It is about JMeter not reusing the SSL >> context if client certs are used. I don't know how to fix and client cert >> usage is not that common, but if you get hit by this, the highly increased >> handshake rate often kills your cpu resources. I had a look at it a few >> months ago, but the fix wasn't obvious to me. Any ideas around here? >> >> Regards, >> >> Rainer >> >> >
