Get the report and increasing heap memory using maven

[Pablo Zanetti]

I had an issue with some long test. The test had an OOM when the report was being calculated. I'm using Gatling 2.1.6 with maven (note that it worked fine in Gatling 2.0.0).

Downloading gatling bundle, then using gatling.sh script, increasing the heap memory and using the -ro option worked fine, but I have two questions:

1- Is it possible to get the report using maven? I've been trying using gatling.reportsOnly and/or gatling.resultsFolder with different options (i.e: mvn gatling:execute -Dgatling.reportsOnly=testname-timestamp) but it is always asking to specify the simulation class and if I put a simulation class it just execute the test instead of getting the report.

2- How can I increase the heap using the maven plugin to avoid the OOM in next executions? Should I use: gatling.gatlingJvmArgs? if yes, I'm seeing that by default it has many other args, should I specify all of them to override the one I want or just passing the -Xmx will work overriding the proper parameter?

[Stéphane LANDELLE]

1- Is it possible to get the report using maven? I've been trying using gatling.reportsOnly and/or gatling.resultsFolder with different options (i.e: mvn gatling:execute -Dgatling.reportsOnly=testname-timestamp) but it is always asking to specify the simulation class and if I put a simulation class it just execute the test instead of getting the report.

In 2.1, you have to pass the simulationClass too, because Gatling needs it to fetch the assertions. You'll no longer have to in 2.2.

mvn gatling:execute -Dgatling.ro=mysimualtion-1436991042135 -Dgatling.sc=MySimulation

2- How can I increase the heap using the maven plugin to avoid the OOM in next executions? Should I use: gatling.gatlingJvmArgs? if yes, I'm seeing that by default it has many other args, should I specify all of them to override the one I want or just passing the -Xmx will work overriding the proper parameter?

Well, give it a try :)

[Pablo Zanetti]

In 2.1, you have to pass the simulationClass too, because Gatling needs it to fetch the assertions. You'll no longer have to in 2.2.

mvn gatling:execute -Dgatling.ro=mysimualtion-1436991042135 -Dgatling.sc=MySimulation

I did: mvn gatling:execute -Dgatling.reportsOnly=mysimulation-1436554579192 -Dgatling.simulationClass=MySimulation

but the problem is that it run the simulation and it doesn't make the report. Also I've played a bit with gatling.resultsFolder just in case the folder is not found, but I couldn't make it work

 

[Stéphane LANDELLE]

Which version of the maven plugin do you use?

It works as expected for me with 2.1.6.

Stéphane Landelle

Lead developer

slan...@gatling.io

 

--
You received this message because you are subscribed to the Google Groups "Gatling User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatling+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Pablo Zanetti]

yup, I'm using maven plugin 2.1.6. Not sure what's wrong here. I'm thinking that perhaps for some reason the folder is not found so it executes the test? I'll continue investigating. Thanks for the help

You received this message because you are subscribed to a topic in the Google Groups "Gatling User Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gatling/7vBF0VM9jKs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gatling+u...@googlegroups.com.

[Stéphane LANDELLE]

Can you reproduce with the demo? https://github.com/gatling/gatling-maven-plugin-demo

Stéphane Landelle

Lead developer

slan...@gatling.io

[Pablo Zanetti]

The demo worked fine and it was helpful to find the issue I had: 

For some reason in the gatling.conf file I had the line: reportsOnly = ""

Commenting out that line solved the problem.

Thanks for the help!

[Stéphane LANDELLE]

Fun!

Glad you finally found it!

Stéphane Landelle

Lead developer

slan...@gatling.io