You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Antonio Gomes Rodrigues <ra...@gmail.com> on 2017/09/18 21:22:38 UTC
Why Start Time & End Time are automatically filled in Thread Group?
Hi,
Something disturb me
Why Start Time & End Time are automatically filled in Thread Group?
When I check Scheduler in Thread Group, Start Time & End Time are
automatically filled with current date
Why?
In a load test execution I have had this error
2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting
ThreadGroup: 2 : SubmitRule
2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting 1
threads for group SubmitRule.
2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Test will stop
on error
2017-09-18 22:25:07,674 INFO o.a.j.t.ThreadGroup: Starting thread group...
number=2 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
2017-09-18 22:25:07,675 ERROR o.a.j.u.JMeterUtils: Error occurred starting
thread group :SubmitRule, error message:End Time (2017/09/18 22:24:51) of
Scheduler for Thread Group SubmitRule is in the past, fix value of End Time
field,
see log file for more details
org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
22:24:51) of Scheduler for Thread Group SubmitRule is in the past, fix
value of End Time field
at
org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadGroup.java:268)
~[ApacheJMeter_core.jar:3.3 r1808647]
at
org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadGroup.java:321)
~[ApacheJMeter_core.jar:3.3 r1808647]
at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
~[ApacheJMeter_core.jar:3.3 r1808647]
at
org.apache.jmeter.engine.StandardJMeterEngine.startThreadGroup(StandardJMeterEngine.java:533)
[ApacheJMeter_core.jar:3.3 r1808647]
at
org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:457)
[ApacheJMeter_core.jar:3.3 r1808647]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
and
2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting
ThreadGroup: 3 : UnloadRule
2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting 1
threads for group UnloadRule.
2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Test will stop
on error
2017-09-18 22:25:07,680 INFO o.a.j.t.ThreadGroup: Starting thread group...
number=3 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
2017-09-18 22:25:07,681 ERROR o.a.j.u.JMeterUtils: Error occurred starting
thread group :UnloadRule, error message:End Time (2017/09/18 22:24:57) of
Scheduler for Thread Group UnloadRule is in the past, fix value of End Time
field,
see log file for more details
org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
22:24:57) of Scheduler for Thread Group UnloadRule is in the past, fix
value of End Time field
at
org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadGroup.java:268)
~[ApacheJMeter_core.jar:3.3 r1808647]
at
org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadGroup.java:321)
~[ApacheJMeter_core.jar:3.3 r1808647]
at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
~[ApacheJMeter_core.jar:3.3 r1808647]
at
org.apache.jmeter.engine.StandardJMeterEngine.startThreadGroup(StandardJMeterEngine.java:533)
[ApacheJMeter_core.jar:3.3 r1808647]
at
org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:457)
[ApacheJMeter_core.jar:3.3 r1808647]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
I think it will be better to don't fill automatically and use a date picker
like
https://github.com/LGoodDatePicker/LGoodDatePicker
What do you think ?
Antonio
Re: Why Start Time & End Time are automatically filled in Thread Group?
Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Thank
Sebb : thanks for the reason
Philippe : me too
I will check if the error I have had it's for all release
And work more in the GUI of JMeter for the next release
Antonio
2017-09-19 9:14 GMT+02:00 sebb <se...@gmail.com>:
> It does help to show the syntax.
>
> On 19 September 2017 at 08:12, Philippe Mouawad
> <ph...@gmail.com> wrote:
> > Hello,
> > I personally never use those fields.
> > I only use duration and rampup.
> >
> > Regards
> >
> > On Tue, Sep 19, 2017 at 8:44 AM, Milamber <mi...@apache.org> wrote:
> >
> >>
> >>
> >> On 18/09/2017 22:22, Antonio Gomes Rodrigues wrote:
> >>
> >>> Hi,
> >>>
> >>> Something disturb me
> >>>
> >>> Why Start Time & End Time are automatically filled in Thread Group?
> >>>
> >>
> >> Probably historical reason (or simplification)
> >>
> >>
> >>> When I check Scheduler in Thread Group, Start Time & End Time are
> >>> automatically filled with current date
> >>>
> >>> Why?
> >>>
> >>
> >> Probably historical reason (or simplification)
> >>
> >>
> >>
> >>> In a load test execution I have had this error
> >>>
> >>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting
> >>> ThreadGroup: 2 : SubmitRule
> >>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting 1
> >>> threads for group SubmitRule.
> >>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Test will
> stop
> >>> on error
> >>> 2017-09-18 22:25:07,674 INFO o.a.j.t.ThreadGroup: Starting thread
> group...
> >>> number=2 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
> >>> 2017-09-18 22:25:07,675 ERROR o.a.j.u.JMeterUtils: Error occurred
> starting
> >>> thread group :SubmitRule, error message:End Time (2017/09/18 22:24:51)
> of
> >>> Scheduler for Thread Group SubmitRule is in the past, fix value of End
> >>> Time
> >>> field,
> >>> see log file for more details
> >>> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
> >>> 22:24:51) of Scheduler for Thread Group SubmitRule is in the past, fix
> >>> value of End Time field
> >>> at
> >>> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadG
> >>> roup.java:268)
> >>> ~[ApacheJMeter_core.jar:3.3 r1808647]
> >>> at
> >>> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadG
> >>> roup.java:321)
> >>> ~[ApacheJMeter_core.jar:3.3 r1808647]
> >>> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.
> java:301)
> >>> ~[ApacheJMeter_core.jar:3.3 r1808647]
> >>> at
> >>> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGro
> >>> up(StandardJMeterEngine.java:533)
> >>> [ApacheJMeter_core.jar:3.3 r1808647]
> >>> at
> >>> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJM
> >>> eterEngine.java:457)
> >>> [ApacheJMeter_core.jar:3.3 r1808647]
> >>> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
> >>>
> >>>
> >>> and
> >>>
> >>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting
> >>> ThreadGroup: 3 : UnloadRule
> >>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting 1
> >>> threads for group UnloadRule.
> >>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Test will
> stop
> >>> on error
> >>> 2017-09-18 22:25:07,680 INFO o.a.j.t.ThreadGroup: Starting thread
> group...
> >>> number=3 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
> >>> 2017-09-18 22:25:07,681 ERROR o.a.j.u.JMeterUtils: Error occurred
> starting
> >>> thread group :UnloadRule, error message:End Time (2017/09/18 22:24:57)
> of
> >>> Scheduler for Thread Group UnloadRule is in the past, fix value of End
> >>> Time
> >>> field,
> >>> see log file for more details
> >>> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
> >>> 22:24:57) of Scheduler for Thread Group UnloadRule is in the past, fix
> >>> value of End Time field
> >>> at
> >>> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadG
> >>> roup.java:268)
> >>> ~[ApacheJMeter_core.jar:3.3 r1808647]
> >>> at
> >>> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadG
> >>> roup.java:321)
> >>> ~[ApacheJMeter_core.jar:3.3 r1808647]
> >>> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.
> java:301)
> >>> ~[ApacheJMeter_core.jar:3.3 r1808647]
> >>> at
> >>> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGro
> >>> up(StandardJMeterEngine.java:533)
> >>> [ApacheJMeter_core.jar:3.3 r1808647]
> >>> at
> >>> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJM
> >>> eterEngine.java:457)
> >>> [ApacheJMeter_core.jar:3.3 r1808647]
> >>> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
> >>>
> >>>
> >>> I think it will be better to don't fill automatically and use a date
> >>> picker
> >>> like
> >>> https://github.com/LGoodDatePicker/LGoodDatePicker
> >>>
> >>> What do you think ?
> >>>
> >>
> >> Why not. If we have the seconds in the time picker.
> >>
> >>
> >>> Antonio
> >>>
> >>>
> >>
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>
Re: Why Start Time & End Time are automatically filled in Thread Group?
Posted by sebb <se...@gmail.com>.
It does help to show the syntax.
On 19 September 2017 at 08:12, Philippe Mouawad
<ph...@gmail.com> wrote:
> Hello,
> I personally never use those fields.
> I only use duration and rampup.
>
> Regards
>
> On Tue, Sep 19, 2017 at 8:44 AM, Milamber <mi...@apache.org> wrote:
>
>>
>>
>> On 18/09/2017 22:22, Antonio Gomes Rodrigues wrote:
>>
>>> Hi,
>>>
>>> Something disturb me
>>>
>>> Why Start Time & End Time are automatically filled in Thread Group?
>>>
>>
>> Probably historical reason (or simplification)
>>
>>
>>> When I check Scheduler in Thread Group, Start Time & End Time are
>>> automatically filled with current date
>>>
>>> Why?
>>>
>>
>> Probably historical reason (or simplification)
>>
>>
>>
>>> In a load test execution I have had this error
>>>
>>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting
>>> ThreadGroup: 2 : SubmitRule
>>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting 1
>>> threads for group SubmitRule.
>>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Test will stop
>>> on error
>>> 2017-09-18 22:25:07,674 INFO o.a.j.t.ThreadGroup: Starting thread group...
>>> number=2 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
>>> 2017-09-18 22:25:07,675 ERROR o.a.j.u.JMeterUtils: Error occurred starting
>>> thread group :SubmitRule, error message:End Time (2017/09/18 22:24:51) of
>>> Scheduler for Thread Group SubmitRule is in the past, fix value of End
>>> Time
>>> field,
>>> see log file for more details
>>> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
>>> 22:24:51) of Scheduler for Thread Group SubmitRule is in the past, fix
>>> value of End Time field
>>> at
>>> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadG
>>> roup.java:268)
>>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>>> at
>>> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadG
>>> roup.java:321)
>>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>>> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
>>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>>> at
>>> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGro
>>> up(StandardJMeterEngine.java:533)
>>> [ApacheJMeter_core.jar:3.3 r1808647]
>>> at
>>> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJM
>>> eterEngine.java:457)
>>> [ApacheJMeter_core.jar:3.3 r1808647]
>>> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
>>>
>>>
>>> and
>>>
>>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting
>>> ThreadGroup: 3 : UnloadRule
>>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting 1
>>> threads for group UnloadRule.
>>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Test will stop
>>> on error
>>> 2017-09-18 22:25:07,680 INFO o.a.j.t.ThreadGroup: Starting thread group...
>>> number=3 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
>>> 2017-09-18 22:25:07,681 ERROR o.a.j.u.JMeterUtils: Error occurred starting
>>> thread group :UnloadRule, error message:End Time (2017/09/18 22:24:57) of
>>> Scheduler for Thread Group UnloadRule is in the past, fix value of End
>>> Time
>>> field,
>>> see log file for more details
>>> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
>>> 22:24:57) of Scheduler for Thread Group UnloadRule is in the past, fix
>>> value of End Time field
>>> at
>>> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadG
>>> roup.java:268)
>>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>>> at
>>> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadG
>>> roup.java:321)
>>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>>> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
>>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>>> at
>>> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGro
>>> up(StandardJMeterEngine.java:533)
>>> [ApacheJMeter_core.jar:3.3 r1808647]
>>> at
>>> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJM
>>> eterEngine.java:457)
>>> [ApacheJMeter_core.jar:3.3 r1808647]
>>> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
>>>
>>>
>>> I think it will be better to don't fill automatically and use a date
>>> picker
>>> like
>>> https://github.com/LGoodDatePicker/LGoodDatePicker
>>>
>>> What do you think ?
>>>
>>
>> Why not. If we have the seconds in the time picker.
>>
>>
>>> Antonio
>>>
>>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: Why Start Time & End Time are automatically filled in Thread Group?
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
I personally never use those fields.
I only use duration and rampup.
Regards
On Tue, Sep 19, 2017 at 8:44 AM, Milamber <mi...@apache.org> wrote:
>
>
> On 18/09/2017 22:22, Antonio Gomes Rodrigues wrote:
>
>> Hi,
>>
>> Something disturb me
>>
>> Why Start Time & End Time are automatically filled in Thread Group?
>>
>
> Probably historical reason (or simplification)
>
>
>> When I check Scheduler in Thread Group, Start Time & End Time are
>> automatically filled with current date
>>
>> Why?
>>
>
> Probably historical reason (or simplification)
>
>
>
>> In a load test execution I have had this error
>>
>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting
>> ThreadGroup: 2 : SubmitRule
>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting 1
>> threads for group SubmitRule.
>> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Test will stop
>> on error
>> 2017-09-18 22:25:07,674 INFO o.a.j.t.ThreadGroup: Starting thread group...
>> number=2 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
>> 2017-09-18 22:25:07,675 ERROR o.a.j.u.JMeterUtils: Error occurred starting
>> thread group :SubmitRule, error message:End Time (2017/09/18 22:24:51) of
>> Scheduler for Thread Group SubmitRule is in the past, fix value of End
>> Time
>> field,
>> see log file for more details
>> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
>> 22:24:51) of Scheduler for Thread Group SubmitRule is in the past, fix
>> value of End Time field
>> at
>> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadG
>> roup.java:268)
>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>> at
>> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadG
>> roup.java:321)
>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGro
>> up(StandardJMeterEngine.java:533)
>> [ApacheJMeter_core.jar:3.3 r1808647]
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJM
>> eterEngine.java:457)
>> [ApacheJMeter_core.jar:3.3 r1808647]
>> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
>>
>>
>> and
>>
>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting
>> ThreadGroup: 3 : UnloadRule
>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting 1
>> threads for group UnloadRule.
>> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Test will stop
>> on error
>> 2017-09-18 22:25:07,680 INFO o.a.j.t.ThreadGroup: Starting thread group...
>> number=3 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
>> 2017-09-18 22:25:07,681 ERROR o.a.j.u.JMeterUtils: Error occurred starting
>> thread group :UnloadRule, error message:End Time (2017/09/18 22:24:57) of
>> Scheduler for Thread Group UnloadRule is in the past, fix value of End
>> Time
>> field,
>> see log file for more details
>> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
>> 22:24:57) of Scheduler for Thread Group UnloadRule is in the past, fix
>> value of End Time field
>> at
>> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadG
>> roup.java:268)
>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>> at
>> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadG
>> roup.java:321)
>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
>> ~[ApacheJMeter_core.jar:3.3 r1808647]
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGro
>> up(StandardJMeterEngine.java:533)
>> [ApacheJMeter_core.jar:3.3 r1808647]
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJM
>> eterEngine.java:457)
>> [ApacheJMeter_core.jar:3.3 r1808647]
>> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
>>
>>
>> I think it will be better to don't fill automatically and use a date
>> picker
>> like
>> https://github.com/LGoodDatePicker/LGoodDatePicker
>>
>> What do you think ?
>>
>
> Why not. If we have the seconds in the time picker.
>
>
>> Antonio
>>
>>
>
--
Cordialement.
Philippe Mouawad.
Re: Why Start Time & End Time are automatically filled in Thread
Group?
Posted by Milamber <mi...@apache.org>.
On 18/09/2017 22:22, Antonio Gomes Rodrigues wrote:
> Hi,
>
> Something disturb me
>
> Why Start Time & End Time are automatically filled in Thread Group?
Probably historical reason (or simplification)
>
> When I check Scheduler in Thread Group, Start Time & End Time are
> automatically filled with current date
>
> Why?
Probably historical reason (or simplification)
>
> In a load test execution I have had this error
>
> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting
> ThreadGroup: 2 : SubmitRule
> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Starting 1
> threads for group SubmitRule.
> 2017-09-18 22:25:07,674 INFO o.a.j.e.StandardJMeterEngine: Test will stop
> on error
> 2017-09-18 22:25:07,674 INFO o.a.j.t.ThreadGroup: Starting thread group...
> number=2 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
> 2017-09-18 22:25:07,675 ERROR o.a.j.u.JMeterUtils: Error occurred starting
> thread group :SubmitRule, error message:End Time (2017/09/18 22:24:51) of
> Scheduler for Thread Group SubmitRule is in the past, fix value of End Time
> field,
> see log file for more details
> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
> 22:24:51) of Scheduler for Thread Group SubmitRule is in the past, fix
> value of End Time field
> at
> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadGroup.java:268)
> ~[ApacheJMeter_core.jar:3.3 r1808647]
> at
> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadGroup.java:321)
> ~[ApacheJMeter_core.jar:3.3 r1808647]
> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
> ~[ApacheJMeter_core.jar:3.3 r1808647]
> at
> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGroup(StandardJMeterEngine.java:533)
> [ApacheJMeter_core.jar:3.3 r1808647]
> at
> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:457)
> [ApacheJMeter_core.jar:3.3 r1808647]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
>
>
> and
>
> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting
> ThreadGroup: 3 : UnloadRule
> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Starting 1
> threads for group UnloadRule.
> 2017-09-18 22:25:07,680 INFO o.a.j.e.StandardJMeterEngine: Test will stop
> on error
> 2017-09-18 22:25:07,680 INFO o.a.j.t.ThreadGroup: Starting thread group...
> number=3 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
> 2017-09-18 22:25:07,681 ERROR o.a.j.u.JMeterUtils: Error occurred starting
> thread group :UnloadRule, error message:End Time (2017/09/18 22:24:57) of
> Scheduler for Thread Group UnloadRule is in the past, fix value of End Time
> field,
> see log file for more details
> org.apache.jorphan.util.JMeterStopTestException: End Time (2017/09/18
> 22:24:57) of Scheduler for Thread Group UnloadRule is in the past, fix
> value of End Time field
> at
> org.apache.jmeter.threads.ThreadGroup.scheduleThread(ThreadGroup.java:268)
> ~[ApacheJMeter_core.jar:3.3 r1808647]
> at
> org.apache.jmeter.threads.ThreadGroup.startNewThread(ThreadGroup.java:321)
> ~[ApacheJMeter_core.jar:3.3 r1808647]
> at org.apache.jmeter.threads.ThreadGroup.start(ThreadGroup.java:301)
> ~[ApacheJMeter_core.jar:3.3 r1808647]
> at
> org.apache.jmeter.engine.StandardJMeterEngine.startThreadGroup(StandardJMeterEngine.java:533)
> [ApacheJMeter_core.jar:3.3 r1808647]
> at
> org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:457)
> [ApacheJMeter_core.jar:3.3 r1808647]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
>
>
> I think it will be better to don't fill automatically and use a date picker
> like
> https://github.com/LGoodDatePicker/LGoodDatePicker
>
> What do you think ?
Why not. If we have the seconds in the time picker.
>
> Antonio
>