2012-06-27 72 views
16

我试图在远程Glassfish服务器(版本3.1.1(build 12))上使用Cargo Maven插件部署web应用程序。 Glassfish服务器以及位于不同Linux服务器上的Java代码(Ubuntu)。我已经在pom文件中配置了所有必要的属性,并在Windows机器上测试了部署。有用。但它在Linux Ubuntu上失败,出现了一些有趣的异常:Cargo插件在Glassfish上部署时抛出CargoException - 部署失败:null

27-Jun-2012 14:36:05 [ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy (default-cli) on project my-web-project-app: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy failed: Deployment has failed: null -> [Help 1] 
27-Jun-2012 14:36:05 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy (default-cli) on project mca-staff-app: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy failed: Deployment has failed: null 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) 
27-Jun-2012 14:36:05   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) 
27-Jun-2012 14:36:05   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) 
27-Jun-2012 14:36:05   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) 
27-Jun-2012 14:36:05   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) 
27-Jun-2012 14:36:05   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 
27-Jun-2012 14:36:05   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
27-Jun-2012 14:36:05   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
27-Jun-2012 14:36:05   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
27-Jun-2012 14:36:05   at java.lang.reflect.Method.invoke(Method.java:597) 
27-Jun-2012 14:36:05   at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) 
27-Jun-2012 14:36:05   at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) 
27-Jun-2012 14:36:05   at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) 
27-Jun-2012 14:36:05   at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) 
27-Jun-2012 14:36:05 Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy failed: Deployment has failed: null 
27-Jun-2012 14:36:05   at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) 
27-Jun-2012 14:36:05   at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) 
27-Jun-2012 14:36:05   ... 19 more 
27-Jun-2012 14:36:05 Caused by: org.codehaus.cargo.util.CargoException: Deployment has failed: null 
27-Jun-2012 14:36:05   at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.waitForProgressObject(AbstractJsr88Deployer.java:285) 
27-Jun-2012 14:36:05   at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.deploy(AbstractJsr88Deployer.java:126) 
27-Jun-2012 14:36:05   at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:56) 
27-Jun-2012 14:36:05   at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:178) 
27-Jun-2012 14:36:05   at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:98) 
27-Jun-2012 14:36:05   at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:311) 
27-Jun-2012 14:36:05   at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) 
27-Jun-2012 14:36:05   ... 20 more 

有没有人在Linux上使用Maven Cargo插件进行远程应用程序部署?或者,也许有人知道这里有什么问题?

+0

你有没有找到解决方案?当我尝试部署到不同的服务器时,我遇到了这个问题,但是如果将主机更改为'localhost',则部署将按预期工作。 – Snekse

+2

这也许相关:http://stackoverflow.com/questions/26599957/cargo-remote-deployment-glassfish-4-1-fails-glassfish-uses-100-cpu(也有一些建议) – wemu

+1

你可以粘贴你的'pom.xml'的一部分描述了货物的部署?另外,你是直接运行它还是由像詹金斯或其他CI服务器运行?我记得使用Cargo + Glassifsh 3是纯粹的痛苦,所以现在我通过Jenkins部署使用Glassfish REST API + curl – PierreF

回答

0

您有没有找到解决方案?当我尝试部署到不同的服务器时,我遇到了这个问题,但是如果将主机更改为本地主机,则部署将按预期工作。

我面临同样的问题,与localhost它一切都很好,当我试图远程部署相同的空错误来了。

我所做的是,我删除了,并在远程服务器上从头开始安装所有东西。因此,我的本地机器和远程服务器上存在相同的Glassfish安装。

之后,一切都很好。

P.S:这可以通过在远程主机上复制本地域来实现。