Created attachment 37015 [details] ActiveThreadsOverTime showing we have a plateau at 1159 Threads instead of 1515 If you add a DebugPostProcessor in the test plan and run a test, you end up with lines in CSV where number of threads and number of threads in Thread Group is equal to 0. As a consequence this breaks the report Active Thread Over Time and any 3rd party plugin report that tries to compute this. Workaround: - Remove DebugPostProcessor See attached Test plan
Created attachment 37016 [details] Test Plan
pmouawad pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/jmeter.git commit 8a02d4b485ddebefb47d18f2273046058cbadafe Author: pmouawad <p.mouawad@ubik-ingenierie.com> AuthorDate: Fri Feb 14 08:31:02 2020 +0100 Bug 64142 - Presence of DebugPostProcessor in Test plan breaks ActiveThread Over time in report due to missing information --- .../main/java/org/apache/jmeter/extractor/DebugPostProcessor.java | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
commit 99a06ac24d77fd15a1adf8bc25bbec5c77c40ea5 AuthorDate: Sun Feb 16 16:29:59 2020 +0100 Seems like our test plans were subject to the bug 64142 Correct the number of reported threads in the expected file, as they have changed with the fixing of bug 64142. Bugzilla Id: 64142 --- bin/testfiles/JDBC_TESTS.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
*** Bug 64176 has been marked as a duplicate of this bug. ***
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5240