jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepak Shetty <shet...@gmail.com>
Subject Re: SyncTimer is messed up if you stop a interrupt a test plan
Date Thu, 25 Aug 2011 17:07:08 GMT
you probably need to raise this in BugZilla if it isnt already there
http://jakarta.apache.org/jmeter/issues.html


On Thu, Aug 25, 2011 at 7:07 AM, GRUWEZ <gruwez@gmail.com> wrote:

> Scenario:
> Use a SyncTimer in your test plan and set it to block up to a number of
> threads, e.g. 5
> Run the test and interrupt it before all 5 threads have been blocked.
> Assume
> 3 threads have been blocked so far.
> Rerun the test and let it run.
> You will notice the SyncTimer will unblock after 2 threads and not 5.
>
> The reason is that when the test is started, the clone() method is called
> on
> the SyncTimer to created a new. Since the test interruption left the
> previous SyncTimer with already 3 threads "registered", this value (3) will
> be used in the cloned SyncTimer
>
> --
> View this message in context:
> http://jmeter.512774.n5.nabble.com/SyncTimer-is-messed-up-if-you-stop-a-interrupt-a-test-plan-tp4734617p4734617.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message