Re: [Resteasy-developers] Building RestEasy

[Sean D. <sea...@gm...>]

Ok, building with 1 thread seems to have worked at least once.  Got these
repeatedly (until I killed the process) at the end (after BUILD SUCCESS):

...
2015-04-02 11:42:55.671::INFO:  Shutdown hook complete
2015-04-02 11:42:56.671::INFO:  Shutdown hook complete
2015-04-02 11:42:57.671::INFO:  Shutdown hook complete
2015-04-02 11:42:58.671::INFO:  Shutdown hook complete
...


On Wed, Apr 1, 2015 at 9:20 PM, Sean Dawson <sea...@gm...>
wrote:

>
> I sent a message to the users list but I didn't get a reply so I'm going
> to try to patch the issue myself.  I cloned the project but almost every
> time I build it, I get this error:
>
> mvn -e -X -DskipTests install
> ...
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 24.094s
> [INFO] Finished at: Wed Apr 01 21:17:33 EDT 2015
> [INFO] Final Memory: 109M/1213M
> [INFO]
> ------------------------------------------------------------------------
> 2015-04-01 21:17:34.136:WARN:oejut.QueuedThreadPool:7 threads could not be
> stopped
> 2015-04-01 21:17:34.140::INFO:  Shutdown hook executing
> 2015-04-01 21:17:34.140::INFO:  Shutdown hook complete
> [ERROR] Failed to execute goal
> org.mortbay.jetty:jetty-maven-plugin:8.1.11.v20130520:run (start-jetty) on
> project callback-tests: Failure: ShutdownMonitorThread already started ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.mortbay.jetty:jetty-maven-plugin:8.1.11.v20130520:run
> (start-jetty) on project callback-tests: Failure
>  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: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.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:57)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  at java.lang.reflect.Method.invoke(Method.java:606)
>  at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failure
>  at
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:539)
>  at
> org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365)
>  at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523)
>  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: java.lang.IllegalStateException: ShutdownMonitorThread already
> started
>  at
> org.eclipse.jetty.server.ShutdownMonitor.setPort(ShutdownMonitor.java:342)
>  at
> org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:514)
>  ... 29 more
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn <goals> -rf :callback-tests
> 2015-04-01 21:17:35.140::INFO:  Shutdown hook complete
> 2015-04-01 21:17:36.140::INFO:  Shutdown hook complete
> 2015-04-01 21:17:37.140::INFO:  Shutdown hook complete
> 2015-04-01 21:17:38.140::INFO:  Shutdown hook complete
> 2015-04-01 21:17:39.140::INFO:  Shutdown hook complete
> Process finished with exit code 1
>
> The first time I enabled -e -X on the command line, it actually completed
> successfully.  But every other time (command line and IntelliJ/IDEA), it's
> failed.
>
>