jakarta-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51331] New: User thread uses same SSL session ID for multiple iterations
Date Tue, 07 Jun 2011 02:50:27 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51331

             Bug #: 51331
           Summary: User thread uses same SSL session ID for multiple
                    iterations
           Product: JMeter
           Version: 2.4
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTTP
        AssignedTo: notifications@jakarta.apache.org
        ReportedBy: juhraffe@yahoo.com
    Classification: Unclassified


When running multiple iterations of a web request using SSL (HTTPS), the first
request sets up a new SSL session, but subsequent requests by the same thread
re-use the existing SSL session set up in the first iteration.  For example,
testing 50,000 single requests by unique users can be tested by setting up 1000
threads with 50 iterations each.  However, because iterations 2 through 50
re-use the SSL session, the results do not represent a real-world multi-user
scenario, since only 1000 SSL sessions are established instead of 50,000. 

Is it possible to start up new SSL sessions for each iteration instead of
re-using existing sessions.  Or, if this is not possible, what would it take to
add this option to JMeter?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org


Mime
View raw message