Bug 60684 - Thread Group: Validate ended prematurely by Scheduler with 0 or very short duration
Summary: Thread Group: Validate ended prematurely by Scheduler with 0 or very short du...
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 3.0
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Keywords: PatchAvailable
Depends on:
Reported: 2017-02-02 20:23 UTC by Philippe Mouawad
Modified: 2017-02-02 20:30 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2017-02-02 20:23:58 UTC
Message on user mailing list:

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.

As an aside, I do have a patch ready for this, which is adding the line
to TreeClonerForValidation.java

Comment 1 Philippe Mouawad 2017-02-02 20:30:03 UTC
Author: pmouawad
Date: Thu Feb  2 20:29:40 2017
New Revision: 1781467

URL: http://svn.apache.org/viewvc?rev=1781467&view=rev
Bug 60684 - Thread Group: Validate ended prematurely by Scheduler with 0 or very short duration
Contributed by Andrew Burton
Bugzilla Id: 60684

Comment 2 The ASF infrastructure team 2022-09-24 20:38:07 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4262