Message on user mailing list: http://mail-archives.apache.org/mod_mbox/jmeter-user/201701.mbox/%3CCABNKX49MpzUW6kMfD%2BQKiQtEbWC-Va_Gth7vWfcueZ8vQv_tWg%40mail.gmail.com%3E 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 tg.setScheduler(false); to TreeClonerForValidation.java Thanks
Author: pmouawad Date: Thu Feb 2 20:29:40 2017 New Revision: 1781467 URL: http://svn.apache.org/viewvc?rev=1781467&view=rev Log: Bug 60684 - Thread Group: Validate ended prematurely by Scheduler with 0 or very short duration Contributed by Andrew Burton Bugzilla Id: 60684 Modified: jmeter/trunk/src/core/org/apache/jmeter/gui/action/validation/TreeClonerForValidation.java jmeter/trunk/xdocs/changes.xml
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4262