search

afranken / jmeter-analysis-maven-plugin

Plugin that parses JMeter result files and computes performance indicators such as average request duration
58 stars 40 forks source link

Reporter fails to generate results on large .jtl file #22

Closed brownad closed 9 years ago

brownad commented 9 years ago

Hi,

I'm using the jmeter-maven-plugin with the jmeter-analyis-maven-plugin, on a long running test (30 mins, > 40,000 requests) the report which relies on the standard generated JTL file, fails to read in the results and thus jmeter fails to exit. It just hangs. On reducing the test time to about 8 mins (20,000 requests) its fine. Is this something with the reporter at play here, or some tweaking that can be done to allow for large files to be parsed in? There are no service errors, or memory problems and can complete without the reporter, if its removed.

Let me know what files you need for investigation.

Using the latest versions of both maven plugins mentioned.

It hangs here, and never continues to next step when things go wrong: [INFO] [INFO] ------------------------------------------------------- [INFO] P E R F O R M A N C E T E S T S [INFO] ------------------------------------------------------- [INFO] [INFO] [info] [debug] JMeter is called with the following command line arguments: -n -t c:\dev \workspace\services\jmeter-myapi-api-performance\src\test\jmeter\myapi-perform ance.jmx -l c:\dev\workspace\services\jmeter-myapi-api-performance\target\jmete r\results\20150218-myapi-performance.jtl -d c:\dev\workspace\services\jmeter-bo otam-api-performance\target\jmeter -j c:\dev\workspace\services\jmeter-myapi-ap i-performance\target\jmeter\logs\myapi-performance.jmx.log [info] Executing test: myapi-performance.jmx

brownad commented 9 years ago

Closing, this looks more to be an issue with jmeter-maven-plugin than the reporter, doesn't even get there...