Re: [Gatling List] Strange problem when I execute the gatling maven plugin in Jenkins

2,600 views
Skip to first unread message

Stéphane Landelle

unread,
Apr 2, 2014, 2:46:27 AM4/2/14
to gat...@googlegroups.com
Hi Andrea,

This plugin is supposed to work with 2M3a.

I think that the problem is related to the environment where your Jenkins runs (which is? your own machine? which OS? Couldbees?).
It seems that somehow, the directory were the simulation was compiled either couldn't be created, or was removed by someone else.

Does it ring a bell?

I've improved logging to help debugging this, but it will only be in the next version: https://github.com/excilys/gatling/issues/1768

Cheers,

Stéphane


2014-04-01 19:33 GMT+02:00 Andrea Bozzoni <andrea....@gmail.com>:
Hello to everybody,
I have a simple project using Gatling 2.0, the maven plugin, version 2.0.0-M3a works well, compile and execute the test scenario, while when I execute the same project like a Jenkins job I receive this error from the plugin (I tried to delete all the maven repository to be sure that the plugin is correctly downloaded):

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.gatling:gatling-maven-plugin:2.0.0-M3a:execute (default) on project testgatlin: Gatling failed.
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
	at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
	at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
Caused by: org.apache.maven.plugin.MojoExecutionException: Gatling failed.
	at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:238)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
	... 30 more
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at io.gatling.mojo.GatlingJavaMainCallerInProcess.runGatling(GatlingJavaMainCallerInProcess.java:83)
	at io.gatling.mojo.GatlingJavaMainCallerInProcess.run(GatlingJavaMainCallerInProcess.java:75)
	at io.gatling.mojo.GatlingMojo.executeGatling(GatlingMojo.java:261)
	at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:235)
	... 32 more
Caused by: java.lang.NullPointerException
	at scala.tools.nsc.interpreter.AbstractFileClassLoader$$anonfun$findAbstractFile$1.apply(AbstractFileClassLoader.scala:31)
	at scala.tools.nsc.interpreter.AbstractFileClassLoader$$anonfun$findAbstractFile$1.apply(AbstractFileClassLoader.scala:30)
	at scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33)
	at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:108)
	at scala.tools.nsc.interpreter.AbstractFileClassLoader.findAbstractFile(AbstractFileClassLoader.scala:30)
	at scala.tools.nsc.interpreter.AbstractFileClassLoader.classBytes(AbstractFileClassLoader.scala:62)
	at scala.tools.nsc.interpreter.AbstractFileClassLoader.findClass(AbstractFileClassLoader.scala:67)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
	at io.gatling.app.SimulationClassLoader$$anonfun$simulationClasses$1.apply(SimulationClassLoader.scala:56)
	at io.gatling.app.SimulationClassLoader$$anonfun$simulationClasses$1.apply(SimulationClassLoader.scala:55)
	at scala.Option.map(Option.scala:145)
	at io.gatling.app.SimulationClassLoader.simulationClasses(SimulationClassLoader.scala:55)
	at io.gatling.app.Gatling.start(Gatling.scala:174)
	at io.gatling.app.Gatling$.fromMap(Gatling.scala:59)
	at io.gatling.app.Gatling$.runGatling(Gatling.scala:80)
	at io.gatling.app.Gatling.runGatling(Gatling.scala)
	... 40 more

Another question what is the version of the maven plugin that can be used with Gatling 1.5?

Thanks,
Andrea

--
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.

Andrea Bozzoni

unread,
Apr 3, 2014, 5:07:05 PM4/3/14
to gat...@googlegroups.com
Hi Stéphane,
the problem is related with the job name in Jenkins, if there are spaces in it the plugin fails with that error. I removed the spaces and everything goes well.
I don't know if the problem is how Jenkins invoke the plugin, but I have other jobs with spaces using other plugins that work well.

In any case my environment is Jenkins running in Tomcat on Mac OS. 

Hope this can help.

Thanks,
Andrea

Stéphane Landelle

unread,
Apr 4, 2014, 1:30:30 AM4/4/14
to gat...@googlegroups.com
OK, so this is the same problem as this: https://github.com/excilys/gatling/wiki/Getting-Started#install
A Jenkins job home is a directory with the name of the job and Gatling doesn't like this kind of path.

Thanks for reporting, and great job for finding out!

Andrea Bozzoni

unread,
Apr 4, 2014, 3:32:09 AM4/4/14
to gat...@googlegroups.com
Hi,
for who is interested, Jenkins give you the possibility to display a job name without spaces with spaces.
In the Jenkins job configuration window is possible to set the job display name like in the screen shot attached.

Cheers,
Andrea
Capture.JPG

Omar Alkaakour

unread,
Jun 17, 2016, 6:08:17 AM6/17/16
to Gatling User Group
Hi Andrea,

I hope all is fine to you,
I have al most the same problem but without jenkins, I have a simple project using Gatling 2.1.7, the maven plugin, version 3.3.9, compile and execute the test scenario, while when I execute the project I receive this error.

[ERROR] Failed to execute goal io.gatling:gatling-maven-plugin:2.1.7:execute (default-cli) on project mindrailherez: Gatling failed. Simulations compilation failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.gatling:gatling-maven-plugin:2.1.7:execute (default-cli) on project mindrailherez: Gatling failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: org.apache.maven.plugin.MojoExecutionException: Gatling failed.
at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:191)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 25 more
Caused by: io.gatling.mojo.CompilationException: Simulations compilation failed.
at io.gatling.mojo.GatlingMojo.executeCompiler(GatlingMojo.java:209)
at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:181)
... 27 more
Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:402)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:164)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:151)
at io.gatling.mojo.Fork.run(Fork.java:81)
at io.gatling.mojo.GatlingMojo.executeCompiler(GatlingMojo.java:207)
... 28 more

Thanks and best regards.

Daniel Hensey

unread,
May 17, 2017, 5:53:25 PM5/17/17
to Gatling User Group
Hi Omar, did you find a resolution to this problem? I have a nearly identical error and can find nothing useful on the internet to help me fix it. I suspect my version on the plugin may not match the version it's supposed to go with in the actual gatling version. Could you share the solution you used?

[ERROR] Failed to execute goal io.gatling:gatling-maven-plugin:2.2.4:execute (default-cli) on project retric-perf-tests: Gatling failed. Simulations compilation failed. Process exited with an error: 255 (Exit value: 255) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.gatling:gatling-maven-plugin:2.2.4:execute (default-cli) on project retric-perf-tests: Gatling failed.
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Gatling failed.
        at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:219)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
        ... 20 more
Caused by: io.gatling.mojo.CompilationException: Simulations compilation failed.
        at io.gatling.mojo.GatlingMojo.executeCompiler(GatlingMojo.java:267)
        at io.gatling.mojo.GatlingMojo.execute(GatlingMojo.java:203)
        ... 22 more
Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 255 (Exit value: 255)
        at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:402)
        at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:164)
        at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:151)
        at io.gatling.mojo.Fork.run(Fork.java:120)
        at io.gatling.mojo.GatlingMojo.executeCompiler(GatlingMojo.java:265)
        ... 23 more
[ERROR] 
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:

Neel Desai

unread,
Jan 30, 2018, 4:44:15 PM1/30/18
to Gatling User Group
Hello Andrea,
Any update on your problem that you have posted here?I am facing similar kind of issue.

Neel Desai

unread,
Feb 20, 2018, 8:46:42 AM2/20/18
to Gatling User Group
Hello @Daniel,

Did you get any solution for your problem? I've exactly the same problem. If you can share your fixing steps then it would be great. Thanks

rsak...@gmail.com

unread,
Mar 11, 2019, 12:20:44 PM3/11/19
to Gatling User Group
Please check your java version ? (Try using 1.8.x)
Reply all
Reply to author
Forward
0 new messages