Periodic error while using html report!

[Rutkovski]

Hello, could you help me, please? Have you ever encountered a problem like the one below while creating an HTML report?

Sometimes it happens with the same code and environments, sometimes it doesn't, which is why I can't find the reason for this problem.

I understand that something is wrong with the report.jtl file at that moment, but I don't know how to fix generating a correct file for the HTML report.
I have an assumption that my test uses too many threads and not all of them have finished writing their data into this file when the HTML reporter started its job. Is it possible?

    +  44435 in 00:00:30 = 1481.2/s Avg:    55 Min:     3 Max:   257 Err:     0 (0.00%) Active: 86 Started: 2966 Finished: 2880
     = 2765327 in 00:32:40 = 1411.0/s Avg:    56 Min:     3 Max:  4121 Err:     0 (0.00%)
    19:37:21.001 [stable-ThreadStarter] INFO  com.blazemeter.jmeter.threads.concurrency.ConcurrencyThreadStarter - Done supplying threads
    19:38:24.216 [Test worker] WARN  org.apache.jmeter.report.core.CsvSampleReader - Short CSV read around line 2796636 of file 'build/reports/jmeterReports/httpReport/report.jtl'. Could only read 3 elements of 17 expected. Data is [1739723840976, 85, GET /applicat]
    19:39:08.865 [Test worker] WARN  org.apache.jmeter.engine.StandardJMeterEngine - Error encountered during shutdown of us.abstracta.jmeter.javadsl.core.listeners.HtmlReporter$AutoFlushingResultCollector@2b329bbd
    java.lang.RuntimeException: org.apache.jmeter.report.dashboard.GenerationException: Error while processing samples: Mismatch between expected number of columns:17 and columns in CSV file:3, check your jmeter.save.saveservice.* configuration or check if line 2796636 in 'build/reports/jmeterReports/httpReport/report.jtl' is complete

P.S. When I checked line 2796636 in 'build/reports/jmeterReports/httpReport/report.jtl', I found that it looks good, and has more than 3 columns

[rabelenda]

Hello, can you please provide more details to try to reproduce the issue you are experiencing? Can you provide an example testplan that allows to reproduce the issue?

You might want to use a log4j2.xml file like this one to display the exception that generates the message "Error encountered during shutdown of us.abstracta.jmeter.javadsl.core.listeners.HtmlReporter$AutoFlushingResultCollector":

<?xml version="1.0" encoding="UTF-8"?>
<Configuration>
  <Appenders>
    <Console name="Console" target="SYSTEM_OUT">
      <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n%ex"/>
    </Console>
  </Appenders>
  <Loggers>
    <Root level="INFO">
      <AppenderRef ref="Console"/>
    </Root>
    <Logger name="org.eclipse.jetty" level="WARN"/>
    <Logger name="org.apache.jmeter" level="WARN"/>
  </Loggers>
</Configuration>

[Rutkovski]

Hello! First of all, thanks for answering!
I've created simple project without any confidential data to demonstrate the problem. You can find it in the branch 'dev':
https://github.com/Rutkovski/jmeter-java-dsl-example/tree/dev
Run it using the following command:
gradle clean test -PTAGS=google-stable (it doesn't matter, that you will get a lot of 429 errors, all test takes about 3 minutes)
In most cases ,I've reproduced the same problem as I described above

Additionally, here is the full log:
jdsl_error.log

[Rutkovski]

Also when I ran test with loglevel INFO I got next log.
"StandardJMeterEngine - Notifying test listeners of end of test"
and ReportGenerator started its work but not all threads were finished at that moment
I use rpsThreadGroup in my tests

    11:26:58.719 [stable-ThreadStarter 1-34] INFO  org.apache.jmeter.threads.JMeterThread - Thread finished: stable-ThreadStarter 1-34
    11:26:58.719 [Test worker] INFO  org.apache.jmeter.engine.StandardJMeterEngine - Notifying test listeners of end of test
    11:26:58.719 [Test worker] INFO  org.apache.jmeter.reporters.ResultCollector - forced flush through ResultCollector#flushFile
    11:26:58.720 [stable-ThreadStarter 1-77] INFO  org.apache.jmeter.threads.JMeterThread - Thread is done: stable-ThreadStarter 1-77
    11:26:58.720 [stable-ThreadStarter 1-77] INFO  org.apache.jmeter.threads.JMeterThread - Thread finished: stable-ThreadStarter 1-77
    11:26:58.723 [Test worker] INFO  org.apache.jmeter.report.dashboard.ReportGenerator - ReportGenerator will use for Parsing the separator: ','
    11:26:58.723 [Test worker] INFO  org.apache.jmeter.report.dashboard.ReportGenerator - Will only generate report from results file: build/reports/jmeterReports/httpReport/report.jtl
    11:26:58.723 [Test worker] INFO  org.apache.jmeter.report.dashboard.ReportGenerator - Reading report generator properties from: /var/folders/qf/m95qzlzx7cvcgnwy1c7nl53m0000gq/T/jmeter-java-dsl14705546471553893187/bin/reportgenerator.properties
    11:26:58.724 [Test worker] INFO  org.apache.jmeter.report.dashboard.ReportGenerator - Merging with JMeter properties
    11:26:58.726 [stable-ThreadStarter 1-70] INFO  org.apache.jmeter.threads.JMeterThread - Thread is done: stable-ThreadStarter 1-70
    11:26:58.726 [stable-ThreadStarter 1-70] INFO  org.apache.jmeter.threads.JMeterThread - Thread finished: stable-ThreadStarter 1-70
...
    11:26:58.731 [Test worker] INFO  org.apache.jmeter.report.config.ReportGeneratorConfiguration - Property 'jmeter.reportgenerator.temp_dir' not found, using default value 'temp' instead.
...
    11:26:58.733 [stable-ThreadStarter 1-16] INFO  org.apache.jmeter.threads.JMeterThread - Thread is done: stable-ThreadStarter 1-16
    11:26:58.733 [stable-ThreadStarter 1-16] INFO  org.apache.jmeter.threads.JMeterThread - Thread finished: stable-ThreadStarter 1-16
    11:26:58.736 [Test worker] INFO  org.apache.jmeter.report.config.ReportGeneratorConfiguration - Will use date range start date: null, end date: null
    11:26:58.738 [Test worker] INFO  org.apache.jmeter.report.config.ReportGeneratorConfiguration - Property 'jmeter.reportgenerator.graph.totalTPS.exclude_controllers' not found, using default value 'false' instead.
...
    11:26:58.746 [stable-ThreadStarter 1-62] INFO  org.apache.jmeter.threads.JMeterThread - Thread is done: stable-ThreadStarter 1-62
    11:26:58.746 [stable-ThreadStarter 1-62] INFO  org.apache.jmeter.threads.JMeterThread - Thread finished: stable-ThreadStarter 1-62
    11:26:58.746 [Test worker] INFO  org.apache.jmeter.report.processor.NormalizerSampleConsumer - Using format, 'ms', to parse timeStamp field
    11:26:58.755 [stable-ThreadStarter 1-51] INFO  org.apache.jmeter.threads.JMeterThread - Thread is done: stable-ThreadStarter 1-51
    11:26:58.755 [stable-ThreadStarter 1-51] INFO  org.apache.jmeter.threads.JMeterThread - Thread finished: stable-ThreadStarter 1-51
...
    11:26:58.935 [stable-ThreadStarter 1-53] INFO  org.apache.jmeter.threads.JMeterThread - Thread is done: stable-ThreadStarter 1-53
    11:26:58.935 [stable-ThreadStarter 1-53] INFO  org.apache.jmeter.threads.JMeterThread - Thread finished: stable-ThreadStarter 1-53
    11:26:59.012 [Test worker] WARN  org.apache.jmeter.report.core.CsvSampleReader - Short CSV read around line 14683 of file 'build/reports/jmeterReports/httpReport/report.jtl'. Could only read 3 elements of 17 expected. Data is [1740040018801, 76, ]
    11:26:59.012 [Test worker] INFO  org.apache.jmeter.report.processor.AbstractSampleConsumer - class org.apache.jmeter.report.processor.AggregateConsumer#stopProducing(): beginDate produced 0 samples

[Rutkovski]

At this moment, I've found two ways to get around this problem but they aren't ideal and have their limitations

1. Add to my testPlan a teardownThreadGroup from classic Jmeter and Thread.sleep:
   teardownThreadGroup(jsr223Sampler ("Thread.sleep (5000):"));
   It helps to wait some time so that all threads will have finished their work. In this case, I waste some time and if there was slow response time and a lots threads it may be not enough.

2. Create an HTML Report after test is finished from a JTL file
   @AfterEach public void tearDown(TestInfo testInfo) { JMeterUtils.setProperty( JMeter.JMETER_REPORT_OUTPUT_DIR_PROPERTY, Paths.get(REPORT_PATH, "httpReport").toString() ); new ReportGenerator(Paths.get(REPORT_PATH, "JtlResults.jtl").toString(), null).generate();
   It works well but I don't think, It will work in case if we use distributed testing (I mean data from the other servers won't be aggregated in the one HTML-report)