jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 61901] New: Support for https.cipherSuites property
Date Wed, 13 Dec 2017 20:11:43 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=61901

            Bug ID: 61901
           Summary: Support for https.cipherSuites property
           Product: JMeter
           Version: 3.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTTP
          Assignee: issues@jmeter.apache.org
          Reporter: jeremy@arnoldzoo.org
  Target Milestone: ---

Created attachment 35609
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35609&action=edit
Patch to support the https.cipherSuites system property

I ran an HTTPS-based JMeter test (using JMeter 3.1) with several hundred users
against one of my servers.  I then switched to a different server to run a
similar test, but the results were terrible. The issue turned out to be that
the new server supported stronger encryption cipher suites, and the stronger
encryption was driving up the CPU on the JMeter client so that it could no
longer support as many users.  In my particular case, it wasn't important to
test with the stronger encryption -- it was more important to be able to scale
up the large number of users.

Both HttpsURLConnection and Apache HttpClient support the https.cipherSuites
system property to allow configuration of what cipher suites are supported by
the client.  But JMeter uses a custom SSLSocketFactory that doesn't use this
property.

JMeter should support the https.cipherSuites system property so that users can
set this value in system.properties when needed.

I've written a patch (generated by Eclipse) against the current trunk code to
add this support.  This fix addressed the issue for my test.

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