Just to follow up - can I just confirm that the performance problems have gone away - now that the issue with the password / NPE has been sorted out?
Seems to be the case from the Bugzilla issue, but it would be useful to get it confirmed here (if you don't mind). Thanks, S On 05/07/07, sebb <[EMAIL PROTECTED]> wrote:
On 05/07/07, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > On Thu, 2007-07-05 at 16:05 +0200, [EMAIL PROTECTED] wrote: > > Okay, it looks like I isolated the issue: There seems to be a problem > > with the SSL manager: Some of the pages we load in the test plans > > contain framesets with frames pointing to https addresses served by our > > proxy. In this scenario the log file shows a NullPointerException (and > > the single HTTP sampler (including embedded page loading) takes up to > > three minutes to execute). > > > > I have submitted this as bugzilla bug #42819. OK, I'll look at that ASAP. > > > > Best regards, > > Jens > > > > > > Jens, > > Are there multiple threads involved in executing that sample? If there > are, it can easily explain the performance degradation you have been > seeing. JMeter now creates a separate SSL context per thread of > execution, which is a _very_ expensive operation. For details see bug > #42506 [1] > > Oleg > > [1] http://issues.apache.org/bugzilla/show_bug.cgi?id=42506 > You can try defining the jmeter property: https.sessioncontext.shared=true to revert to the previous behaviour. What happens if you try that?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
