jmeter-issues mailing list archives

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

--- Comment #2 from Jeremy Arnold <jeremy@arnoldzoo.org> ---
I apologize for the confusion between System property vs JMeter property.  I
intended for this to be a System property (set in system.properties) to match
the behavior of HttpsURLConnection / HttpClient.  But when I wrote the patch I
was following the example of https.socket.protocols, and thus used
JMeterUtils.getPropDefault.

Since JMeterUtils.loadJMeterProperties initializes its local properties using
"Properties p = new Properties(System.getProperties())", I believe the code
does work with System properties in addition to JMeter properties.  (In my
testing, I set the value in the system.properties file.)

I'd be happy to update the patch to use System.getProperty instead so this
value can only be set as a System property and not a JMeter property.  Please
let me know if that's your preference.


I haven't gotten completely to the bottom of the performance issue.  In my test
the JMeter system CPU was maxed out, primarily performing SSL handshakes.  I
wouldn't expect quite as big of a difference in CPU utilization between the two
cipher suites that were being used.  My suspicion was that one of them was
being hardware accelerated and the other not, but I have not yet confirmed
that.

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