jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From RP Schell <>
Subject Re: Certificates are switching on threads in the middle of a test run
Date Mon, 05 May 2014 22:34:14 GMT
Thanks for the feedback!

Yup, as stated I have tried https.use.cached.ssl.context=false,
HttpClient4, and https.sessioncontext.shared=false without success.
Setting https.use.cached.ssl.context to true seems to be do better
because the user switching does not happen as frequently, but it still
happens setting that option to true or false.

In answer to your question, we typically put the keystore
configuration under the test plan itself at the same level as the
thread group that is being defined.  The plan itself only defines a
single thread group.  We have tried putting the keystore configuration
under the thread group itself.  THIS MAKES NO DIFFERENCE.  Putting it
at the top level or under the thread group when there is only one
thread group defined has the same behavior.

I had not tried using the keystore configuration with a CSV data set
configuration.  Thanks for that suggestion.  I tried an experiment
with that.  The CSV allows the control of the what certificate is used
and in what order.  However, it does not solve the ultimate problem of
JMeter switching users.  The CSV data set configuration simply causes
JMeter to switch users as defined in the order of the CSV instead.

I am seeing a pattern emerge from using the CSV though.  Our test
users are numbered chronologically (e.g., user0, user1, user2, user3,
etc).  Every 5 loops through the JMeter test, the user identified is 5
numbers higher than before.  For example, the test starts at coming in
as user 0.  On the 5th looping of the test in that thread group, the
user is now identified as user 4, and we start getting errors because
the server expected us to still be user 0.

Again, it looks like JMeter is switching users on me when it restarts
the looping of the test plan.  How do we control this.  It seems none
of the options I have mentioned trying allow for it.  Thanks!


On Tue, Apr 29, 2014 at 4:12 PM, UBIK LOAD PACK Support
<> wrote:
> Hello,
> As per:
> https.use.cached.ssl.context must be set to false and httpclient4 must be
> used
> Don't use:
>  https.sessioncontext.shared=false
> Also it is much better since 2.11 to use :
> Variable name holding certificate aliasVariable name that will contain the
> alias to use for authentication by client certificate. Variable value will
> be filled from CSV Data Set for example. In the screenshot,
> "certificat_ssl" will also be a variable in CSV Data Set.False
> Read doc on start and end index to be sure you configure them correctly
> You speak about different thread groups, where do you put keystore config ?
> Regards
> @ubikloadpack
> On Tuesday, April 29, 2014, RP Schell <> wrote:
>> Hey everyone,
>> We are attempting to simulate a large user load (thousands) on our
>> service using JMeter 2.11.  To facilitate this, we have created a JKS
>> keystore containing 4000 unique PKI certificates.  We have set the
>> appropriate options for and
>> and added a Keystore Configuration
>> component with an alias start index of 0 and alias end index of 3999.
>> We verified that we can access the system as unique users using JMeter
>> with this set up.
>> We started seeing some strange results come back from the JMeter test
>> runs and determined that the errors returned by our web server were
>> due to the user certificate switching in the middle of a test run for
>> a given JMeter thread.  More specifically, we added a HTTP request
>> that gives back some indication of who we are logged in as at the end
>> of the test run loop.  It appears every thread in JMeter is switching
>> the user it is coming in as about every 5 loops of our test run.  This
>> occurs for each thread whether we set it to run with one or multiple
>> threads.
>> This causes problems for our testing as some HTTPS requests assume we
>> are still the same user and will deny access if the user switches
>> mid-way through the test run.  We verified that
>> https.sessioncontext.shared=false and
>> https.use.cached.ssl.context=true is set in the
>> file.  We did try other combinations of these two options w/o success.
>> We also tried setting the implementation for HTTP requests to
>> HTTPClient3.1 as well as HTTPClient4.  The behavior is the same.
>> Is this behavior intended by JMeter?  The only way I can prevent the
>> certificate from switching mid-test is to set the alias start and end
>> index to the same number in the Keystore Configuration component.  Of
>> course, this is not what we want as it locks all JMeter threads into
>> running as the exact same user and does not allow proper simulation of
>> a multi-user load.
>> Any insight into multi-user certificate loading in JMeter is much
>> appreciated.  Thanks!
>> -Bill
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: <javascript:;>
>> For additional commands, e-mail:<javascript:;>
> --
> Regards
> Ubik Load Pack <> Team
> Follow us on Twitter <>
> Cordialement
> L'équipe Ubik Load Pack <>
> Suivez-nous sur Twitter <>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message