Mailing-List: contact issues-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@jmeter.apache.org
From: bugzilla@apache.org
To: issues@jmeter.apache.org
Subject: [Bug 60684] New: Thread Group: Validate ended prematurely by
 Scheduler
Date: Thu, 02 Feb 2017 20:23:58 +0000
Message-ID: <bug-60684-58895@https.bz.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
MIME-Version: 1.0
archived-at: Thu, 02 Feb 2017 20:24:07 -0000

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

            Bug ID: 60684
           Summary: Thread Group: Validate ended prematurely by Scheduler
           Product: JMeter
           Version: 3.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: p.mouawad@ubik-ingenierie.com
  Target Milestone: ---

Message on user mailing list:
http://mail-archives.apache.org/mod_mbox/jmeter-user/201701.mbox/%3CCABNKX4=
9MpzUW6kMfD%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 =3D ${__P(user.sports.usercount,0)}
Duration (Scheduler enabled) =3D ${__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

--=20
You are receiving this mail because:
You are the assignee for the bug.=