2016-03-18 24 views
1

即使上下文肯定沒有在/etc/tomcat8/server.xml中定義,當通過Maven部署與Jenkins的應用程序時,出現以下錯誤(服務器上沒有其他server.xml)。通常,在重新啓動Tomcat後部署工作,但這個問題變得非常煩人,因爲它經常發生。可能是什麼原因?Jenkins Tomcat部署:上下文在server.xml中定義,可能不會部署

謝謝!

Redeploying [/var/lib/jenkins/jobs/MYAPP Java Backend/workspace/MYAPP/target/MYAPP-0.0.1-SNAPSHOT.war] 
    Undeploying [/var/lib/jenkins/jobs/MYAPP Java Backend/workspace/MYAPP/target/MYAPP-0.0.1-SNAPSHOT.war] 
ERROR: Build step failed with exception 
org.codehaus.cargo.container.ContainerException: Failed to undeploy [/var/lib/jenkins/jobs/MYAPP Java Backend/workspace/MYAPP/target/MYAPP-0.0.1-SNAPSHOT.war] 
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.undeploy(AbstractTomcatManagerDeployer.java:140) 
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:178) 
    at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73) 
    at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116) 
    at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103) 
    at hudson.FilePath.act(FilePath.java:990) 
    at hudson.FilePath.act(FilePath.java:968) 
    at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103) 
    at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61) 
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) 
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) 
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) 
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047) 
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) 
    at hudson.model.Run.execute(Run.java:1763) 
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) 
    at hudson.model.ResourceController.execute(ResourceController.java:98) 
    at hudson.model.Executor.run(Executor.java:410) 
Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Context /MYAPP is defined in server.xml and may not be undeployed 

    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:566) 
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:480) 
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.undeploy(TomcatManager.java:420) 
    at org.codehaus.cargo.container.tomcat.Tomcat7xRemoteDeployer.performUndeploy(Tomcat7xRemoteDeployer.java:62) 
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.undeploy(AbstractTomcatManagerDeployer.java:130) 
    ... 17 more 
org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Context /MYAPP is defined in server.xml and may not be undeployed 

    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:566) 
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.invoke(TomcatManager.java:480) 
    at org.codehaus.cargo.container.tomcat.internal.TomcatManager.undeploy(TomcatManager.java:420) 
    at org.codehaus.cargo.container.tomcat.Tomcat7xRemoteDeployer.performUndeploy(Tomcat7xRemoteDeployer.java:62) 
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.undeploy(AbstractTomcatManagerDeployer.java:130) 
    at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:178) 
    at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:73) 
    at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116) 
    at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103) 
    at hudson.FilePath.act(FilePath.java:990) 
    at hudson.FilePath.act(FilePath.java:968) 
    at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103) 
    at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61) 
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) 
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) 
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) 
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047) 
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) 
    at hudson.model.Run.execute(Run.java:1763) 
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) 
    at hudson.model.ResourceController.execute(ResourceController.java:98) 
    at hudson.model.Executor.run(Executor.java:410) 
Build step 'Deploy war/ear to a container' marked build as failure 
Finished: FAILURE 
+0

你有沒有深究這一點。我經歷了與tomcat經理文本http調用類似的東西。 – twinj

+0

通過salt使用管理器API時剛遇到同樣的錯誤。在我們的案例中,似乎是因爲部署需要很長時間,而且(我懷疑)也是部署不當,導致部署重疊的部分仍在部署。解決方法是增加salt連接管理器的超時時間。 – user3452758

回答

-2

在我的情況下,這些錯誤消息發生時我在server.xml又增加了<Context>配置。

我在server.xml中設置了[Context docBase="MyApp" path="/" source="{MyApp.location}"]

嘗試移除server.xml中的<Context>配置。

+1

「即使上下文肯定沒有在/etc/tomcat8/server.xml中定義」 – twinj