When Timer needs to terminate thread, it logs: - 2020-04-22 22:33:45,487 INFO o.a.j.t.JMeterThread: Stopping Thread: org.apache.jorphan.util.JMeterStopThreadException: The thread is scheduled to stop in -70320 ms and the throughput timer generates a delay of 159461. JMeter (as of 4.0) does not support interrupting of sleeping threads, thus terminating the thread manually. This value -70320 is incorrect.
This is an automated email from the ASF dual-hosted git repository. pmouawad pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/jmeter.git The following commit(s) were added to refs/heads/master by this push: new 0772c1d Bug 64381 - PreciseThroughputTimer: On termination, log message contains negative value 0772c1d is described below commit 0772c1d97e49aa6c5e615f1fc02ba7bd215c710b Author: pmouawad <p.mouawad@ubik-ingenierie.com> AuthorDate: Sun Apr 26 18:08:42 2020 +0200 Bug 64381 - PreciseThroughputTimer: On termination, log message contains negative value Also avoid calling System.currentTimeMillis() too much times --- .../jmeter/timers/poissonarrivals/PreciseThroughputTimer.java | 11 ++++++----- xdocs/changes.xml | 1 + 2 files changed, 7 insertions(+), 5 deletions(-)
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5298