jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62734] Jmeter HTTPS tests with tlsv1.2 and 256 bit AES ciphers only lead to 5-10% SSLHandShakeErrors
Date Tue, 18 Sep 2018 21:34:46 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62734

Philippe Mouawad <p.mouawad@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
           Keywords|                            |FixedInTrunk
   Target Milestone|---                         |JMETER_5.0
           Hardware|PC                          |All
         Resolution|---                         |DUPLICATE

--- Comment #3 from Philippe Mouawad <p.mouawad@ubik-ingenierie.com> ---
(In reply to Matty D from comment #2)
> Philippe -- Thank you for a quick reply!
> 
> I was able to run a quick test of the latest nightly build and can confirm
> that no SSL errors were encountered and it appears you are indeed correct
> that this must have been fixed prior.  If possible, could you point me at
> what those prior fix or bug tickets might be so I can try to understand the
> issue fix in more detail?
> 
> Thanks,
> Matt

See Bug 58807.
In previous versions, we were too aggressive on ssl handshakes since we would
reset state too often.
So that might be the explanation of ypur issue.
Note that it might indirectly reveal an issue with your server at high scale
only if your jmeter injector was not affected by high cpu consumption 

JMeter 5.0 will be out tomorrow with this fix and lot of new features.

Thanks for feedback

*** This bug has been marked as a duplicate of bug 58807 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message