Menu
▾
▴
resteasy-developers
|
From: Sean D. <sea...@gm...> - 2015-04-02 01:20:52
|
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. |
|
From: Romain P. <be...@re...> - 2015-06-04 08:39:28
Attachments:
test.disable.txt
|
Hi all, i'm trying to build locally RestEasy, and I had to disable part of the tests to do so (see diff joined). I wonder if this is a "known issue" or if I am missing part of the puzzle (maybe I need to have some server running, or run a specific task before running 'mvn install' or maybe this is tie to my local config...) -- Best Regards, http://developerblog.redhat.com/author/rpelisse/ Romain PELISSE Software Engineer Red Hat GmbH Zieher Business Centers, Am Treptower Park 75, 12435 Berlin Germany Cell (DE): +49 (0) 172-7442628 Cell (FR): +33 (0) 669304455 Delivering value year after year Red Hat ranks # 1 in value among software vendors http://www.redhat.com/promo/vendor/ Freedom...Courage...Commitment...Accountability Red Hat GmbH, http://www.de.redhat.com/ Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Charles Peters |
|
From: Ron S. <rs...@re...> - 2015-06-10 23:17:21
|
Hi Romain, I just checked out, built, and tested the master branch from https://github.com/resteasy/Resteasy. Here are a few remarks that might help. 1. When I clean and build, I always get a failure in the callback-tests module in async-http-servlet-3.0. I think it might be specific to linux, and I haven't taken the time to figure it out. I just wrote a script mvn clean install -DskipTests=true; mvn clean install -DskipTests=true -rf :callback-tests I run that, and then I run mvn test 2. I've never had a problem with the examples module. What are you seeing? One possibility is that you have something running that's using the 8080 port. I wrote a script (killportuser) for that: > #!/bin/tcsh > > if ($#argv < 1) then > echo usage: killportuser port > exit > endif > > set port="$1" > echo Looking for process using port $port > set p = `fuser -n tcp $port,,` > if ( x${p}x == xx ) then > echo $port is not in use > else > echo killing process $p > kill -9 $p > endif [Yeah, I admit it - I use tcsh.] 3. There are some tests in jaxb, written by me, that started causing a problem at some point. Look at the after() method in org.jboss.resteasy.test.charset.TestCharsetExpand and TestCharsetNoExpand. It seems that when you add a line > @AfterClass > public static void after() throws Exception > { > process.destroy(); > Thread.sleep(5000); // <=== ADD > System.out.println("Process destroyed."); > } it prevents a later test from failing. Could you try that and see if you have the same result? I should commit that change. 4. As for the security modules, I don't have any problems. What are you seeing? Do you have the "unlimited strength JCE policy files"? If not, that could cause failures. See http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html for jdk 8. -Ron On 06/04/2015 04:39 AM, Romain PELISSE wrote: > Hi all, > > i'm trying to build locally RestEasy, and I had to disable part of the tests to do so (see diff joined). I wonder if this is a "known issue" or if I am missing > part of the puzzle (maybe I need to have some server running, or run a specific task before running 'mvn install' or maybe this is tie to my local config...) > -- > Best Regards, > http://developerblog.redhat.com/author/rpelisse/ > > Romain PELISSE > Software Engineer > Red Hat GmbH > Zieher Business Centers, > Am Treptower Park 75, > 12435 Berlin > Germany > Cell (DE): +49 (0) 172-7442628 > Cell (FR): +33 (0) 669304455 > > Delivering value year after year > > > Red Hat ranks # 1 in value among software vendors > > > http://www.redhat.com/promo/vendor/ > > > Freedom...Courage...Commitment...Accountability > > Red Hat GmbH, http://www.de.redhat.com/ Registered seat: Grasbrunn, > Commercial register: Amtsgericht Muenchen, HRB 153243, > Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Charles Peters > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-developers |
|
From: Sean D. <sea...@gm...> - 2015-04-02 15:46:02
|
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. > > |
|
From: Bill B. <bb...@re...> - 2015-04-07 13:41:27
|
Ya, I need to remove the Jetty dependencies where possible and move to Undertow. On 4/2/2015 11:45 AM, Sean Dawson wrote: > > 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... > <mailto: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. > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-developers > -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |
|
From: Ron S. <rs...@re...> - 2015-04-26 01:17:07
|
Hey Sean, I never looked into the problem, but it happened to me so much that I just wrote a script: mvn clean install -DskipTests=true; mvn clean install -DskipTests=true -rf :callback-tests -Ron "Ain't that pretty at all" - Warren Zevon On 04/07/2015 09:41 AM, Bill Burke wrote: > Ya, I need to remove the Jetty dependencies where possible and move to > Undertow. > > On 4/2/2015 11:45 AM, Sean Dawson wrote: >> 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... >> <mailto: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. >> >> >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for all >> things parallel software development, from weekly thought leadership blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> >> >> >> _______________________________________________ >> Resteasy-developers mailing list >> Res...@li... >> https://lists.sourceforge.net/lists/listinfo/resteasy-developers >> |
Thanks for helping keep SourceForge clean.
X