https://bz.apache.org/bugzilla/show_bug.cgi?id=58807
--- Comment #14 from [email protected] --- Hi, well in jmeter 2.13 i had the following (so far not clear to me) issue with https where the https WAS mutual ssl. I set up the ssl debug on and watched what happend with my http samplers. I had a java key store whith 2 client certs. I had a key store configuration element which starts at 0 and ends at 1 (2 elements). Now i had one thread group and 2 http samplers both pointing to the same https server. One sampler was targeting https://server/uri and the second ../uri2. Now i had the following problem. The first http sampler picked the first ssl cert from my keystore [0] made a mutual ssl connection and execute .../uri. -great. The second http sampler DOES NOT REUSE the connection and DOES NOT executed the ../uri2 BUT the second http sampler made a NEW connection (ssl) and picked a NEW client cert from the keystore [1] It was STILL the SAME Thread just the next http sampler. It was a mess because the user with the client cert on [1] was not allowed to execute the ../uri2. Then...i changed the parameter "https.use.cached.ssl.context" and put value "true". I have no idea why...but it WORKED?!?. Means the first http sampler did mutual ssl and execute ../uri The second http sampler did NOT the handshake again but execute the ../uri2 as the same user as the first sampler. perfect. But why? -- You are receiving this mail because: You are the assignee for the bug.
