Quantcast

Thread Group Validate ended prematurely by Scheduler

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Thread Group Validate ended prematurely by Scheduler

Andrew Burton
Hi all,

I have a thread group that has about 10-12 consecutive samplers, and was
using the Validate option to debug through these. I noticed that not all
the samplers were being invoked, and in the jmeter.log I can see the
following line:

2017/01/30 13:41:54 INFO  - jmeter.threads.JMeterThread: Stopping because
end time detected by thread: Sports 1-1

Does this mean that the Validate feature is still subject to Scheduler
duration? Currently, I use the following:

Threads = ${__P(user.sports.usercount,0)}
Duration (Scheduler enabled) = ${__P(user.sports.duration)}

Both parameter options are not specified, i.e. they will take default
values of 0 and 1 respectively.

I suspect that since I haven't explicitly set a second default-value
parameter to __P() function for the Duration setting, it's setting it to 1
as per the __P() docs, but I was expecting Validate would ignore
duration/endtime setting as it does for Threads.

Can anyone advise their experience with Validate, or whether this is a bug?

As an aside, I do have a patch ready for this, which is adding the line
                tg.setScheduler(false);
to TreeClonerForValidation.java

Thanks

Andrew
pmd
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Thread Group Validate ended prematurely by Scheduler

pmd
Hi,
Fixed in:

https://bz.apache.org/bugzilla/show_bug.cgi?id=60684

Thankd for patch
Regards

On Tuesday, January 31, 2017, Andrew Burton <[hidden email]>
wrote:

> Hi all,
>
> I have a thread group that has about 10-12 consecutive samplers, and was
> using the Validate option to debug through these. I noticed that not all
> the samplers were being invoked, and in the jmeter.log I can see the
> following line:
>
> 2017/01/30 13:41:54 INFO  - jmeter.threads.JMeterThread: Stopping because
> end time detected by thread: Sports 1-1
>
> Does this mean that the Validate feature is still subject to Scheduler
> duration? Currently, I use the following:
>
> Threads = ${__P(user.sports.usercount,0)}
> Duration (Scheduler enabled) = ${__P(user.sports.duration)}
>
> Both parameter options are not specified, i.e. they will take default
> values of 0 and 1 respectively.
>
> I suspect that since I haven't explicitly set a second default-value
> parameter to __P() function for the Duration setting, it's setting it to 1
> as per the __P() docs, but I was expecting Validate would ignore
> duration/endtime setting as it does for Threads.
>
> Can anyone advise their experience with Validate, or whether this is a bug?
>
> As an aside, I do have a patch ready for this, which is adding the line
>                 tg.setScheduler(false);
> to TreeClonerForValidation.java
>
> Thanks
>
> Andrew
>


--
Cordialement.
Philippe Mouawad.
Loading...