hi Philippe, I think I have found the difference between the nightly build and the released 2.6
While running with the gc switches that you suggested, I found this line in the jmeter.log of the released 2.6 jmeter.protocol.http.sampler.HTTPSamplerBase: Reuse SSL session context on subsequent iterations: true Nightly: if there is an authorization manager, it will attempt basic authentication only on requests where the server sends a challenge Released 2.6: if there is an authorization manager, it will always attempt basic authentication. The api that I am testing is not sending any username/password. Now, I think that entering a Bugzilla issue is probably not required. However, I did not see a mention of this change on http://jmeter.apache.org/changes.html, so it's possible that other users will find the same problem. I think the setting in jmeter.properties that changed is #https.use.cached.ssl.context=true If I get it right, the proper solution, if one initial ssl http call is required, is to put the authorization manager only in the relevant Thread Group, otherwise it will have a global effect (i.e. also on http calls where the server does not challenge). Or am I missing something obvious? thanks Ivan -- View this message in context: http://jmeter.512774.n5.nabble.com/Performance-difference-between-released-2-6-and-nighly-r1095243-tp5522066p5525155.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
