[
https://issues.jenkins-ci.org/browse/JENKINS-12133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159907#comment-159907
]
Alessandro Oliveira commented on JENKINS-12133:
-----------------------------------------------
anybody found a workaround for this?
> need to use redeploy, or force deploy for glassfish
> ---------------------------------------------------
>
> Key: JENKINS-12133
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12133
> Project: Jenkins
> Issue Type: Bug
> Components: deploy
> Reporter: Derek Knapp
>
> After the 1st build I get the following exception
> If I were deploying using the command line, I would simply add --force to the
> command, for example
> {code}
> asadmin deploy --force /root/itrac/itmems4/itmems4-ear/target/itmems4-ear.ear
> {code}
> Simply adding --force to the command should do the trick, as there is no
> negative side effects.
> {code}
> Deploying
> /root/.jenkins/jobs/itmems4/workspace/itmems4-ear/target/itmems4-ear.ear to
> container GlassFish 3.x Remote
> ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to
> exception
> org.codehaus.cargo.util.CargoException: Deployment has failed: Action failed
> Deploying application to target server failed; Error occurred during
> deployment: Application with name itmems4-ear is already registered. Either
> specify that redeployment must be forced, or redeploy the application. Or if
> this is a new deployment, pick a different name. Please see server.log for
> more details.
> at
> org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.waitForProgressObject(AbstractJsr88Deployer.java:220)
> at
> org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.deploy(AbstractJsr88Deployer.java:76)
> at
> org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:142)
> at
> hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:60)
> at
> hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:86)
> at
> hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:73)
> at hudson.FilePath.act(FilePath.java:783)
> at hudson.FilePath.act(FilePath.java:765)
> at
> hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:73)
> at
> hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:45)
> at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
> at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692)
> at
> hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:1014)
> at
> hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
> at hudson.model.Run.run(Run.java:1429)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:238)
> Finished: FAILURE
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
