jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 60768] Jmeter: testing with TLS cert creates new connection with every request
Date Sat, 25 Feb 2017 08:21:01 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=60768

--- Comment #2 from digant@yahoo-inc.com ---
Created attachment 34777
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34777&action=edit
Test file

Yes, Adding NoopUserTokenHandler helps.

Here are the requested details:

- your test plan ? Cookie Manager , pause times between request ?

  Attached the test plan. I have not removed the hostname and enpoint details,
as I can not share those values. 
  There is a default cookie manager for the test.
  There is no pause between requests. This test tries to get maximum output
from server.

- What makes you think a new connection is created for every request ?
  Run the test with with thread (with forever loop), with keep alive on. This
test should try to use the same connection (as there is no pause between
requests). You can verify the connection details by running command in your
mac:
   netstat  | grep "*.https"

   It could have output like:
   tcp4       0   1253  unknown-xx-xx-xx.12345 hostabcd.xyz...https ESTABLISHED

   Here 12345 is the connection id. Running above command quickly should not
change the connection id.

- More details:
  TLS cert used is TLSv1.2
  Only changed configuration in Jmeter are:
    System.properties file:
        javax.net.ssl.keyStore=<location_of_jks file>
        javax.net.ssl.keyStorePassword=<password>

I have tested my test case with nightly build also without any success.

Please let me know, if any more details are required.

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