Cargo error when shutting down Jetty container

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Cargo error when shutting down Jetty container

LeeRosenberg
This post has NOT been accepted by the mailing list yet.
I'm setting up Cargo with Jetty in an attempt to gather JaCoCo code coverage metrics.  My test suite will run properly and I don't see any errors until the very end.  At that point, I get a FATAL ERROR and the following error/stack trace:

org.codehaus.cargo.container.ContainerException: Failed to stop the Jetty 9.1.4.v20140401 container. Check the [........../cargo/logs/container.log] file containing the container logs for more details.
        at org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:303)
        at org.codehaus.cargo.maven2.ContainerStopMojo.doExecute(ContainerStopMojo.java:49)
        at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:432)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        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:601)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.codehaus.cargo.util.CargoException: Jetty command failed: exit code was -4
        at org.codehaus.cargo.container.jetty.Jetty6xInstalledLocalContainer.invoke(Jetty6xInstalledLocalContainer.java:232)
        at org.codehaus.cargo.container.jetty.Jetty7xInstalledLocalContainer.invoke(Jetty7xInstalledLocalContainer.java:89)
        at org.codehaus.cargo.container.jetty.Jetty6xInstalledLocalContainer.doStop(Jetty6xInstalledLocalContainer.java:150)
        at org.codehaus.cargo.container.spi.AbstractInstalledLocalContainer.stopInternal(AbstractInstalledLocalContainer.java:324)
        at org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:283)
        ... 21 more
org.codehaus.cargo.util.CargoException: Jetty command failed: exit code was -4
        at org.codehaus.cargo.container.jetty.Jetty6xInstalledLocalContainer.invoke(Jetty6xInstalledLocalContainer.java:232)
        at org.codehaus.cargo.container.jetty.Jetty7xInstalledLocalContainer.invoke(Jetty7xInstalledLocalContainer.java:89)
        at org.codehaus.cargo.container.jetty.Jetty6xInstalledLocalContainer.doStop(Jetty6xInstalledLocalContainer.java:150)
        at org.codehaus.cargo.container.spi.AbstractInstalledLocalContainer.stopInternal(AbstractInstalledLocalContainer.java:324)
        at org.codehaus.cargo.container.spi.AbstractLocalContainer.stop(AbstractLocalContainer.java:283)
        at org.codehaus.cargo.maven2.ContainerStopMojo.doExecute(ContainerStopMojo.java:49)
        at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:432)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        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:601)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

I don't see any errors in the container.log file or the local trace log from the service.  I'd previously run with an older version (jetty7x) and was seeing the same thing.  I'm using Cargo version 1.4.8.

Does anyone know what might be causing this?  I can certainly share out relevant parts from my pom.xml if necessary.

Thanks,
Lee Rosenberg