Error Writing Request Body To Server Cargo
Contents |
here for a quick overview of the error writing request body to server tomcat site Help Center Detailed answers to any questions
Jenkins Error Writing Request Body To Server
you might have Meta Discuss the workings and policies of this site About Us
Error Writing Request Body To Server Java
Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs
Error Writing Request Body To Server Git Eclipse
Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Unable to deploy to Tomcat7 from cargo up java io ioexception error writing request body to server vote 8 down vote favorite I'm trying to deploy to a remote Tomcat7 with Cargo from Maven over https. I've set up manager-script role and I've succeeded so far as to have been able to undeploy an app remotely. What I have looks like this:
Sign in Pricing ant tomcat error writing request body to server Blog Support Search GitHub This repository Watch 18 Star httpurlconnection error writing request body to server 25 Fork 19 JetBrains/teamcity-deployer-plugin Code Issues 20 Pull requests 1 Projects 0 Pulse Graphs New issue http://stackoverflow.com/questions/7675243/unable-to-deploy-to-tomcat7-from-cargo Deploy to Tomcat 7 fails with java.io.Exception: Error writing request body to server #54 Closed peraage opened this Issue Mar 23, 2015 · 2 comments Projects None yet Labels None yet https://github.com/JetBrains/teamcity-deployer-plugin/issues/54 Milestone No milestone Assignees No one assigned 2 participants peraage commented Mar 23, 2015 Deployment fails as stated above, while deployment from same machine as agent using curl works fine. Looks like the agent succeeds with listing webs, but fails to deploy. Logs from Tomcat server: 127.0.0.1 - deployer [23/Mar/2015:11:21:33 +0100] "GET /manager/text/list HTTP/1.0" 200 225 Logs from build agent: [2015-03-23 11:20:37,690] ERROR - jetbrains.buildServer.AGENT - org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/buildagent/buildagent/work/a0f3b04d061b2cc0/auksjonen-prototype -1.0.0-SNAPSHOT.war] jetbrains.buildServer.RunBuildException: org.codehaus.cargo.container.ContainerException: Failed to deploy [/home/buildagent/buildagent/work/a0f3b04d061b2cc0/auksjonen-prototype-1.0.0-SNAPSHOT.war] at jetbrains.buildServer.deployer.agent.cargo.CargoBuildProcessAdapter.runProcess(CargoBuildProcessAdapter.java:104) at jetbrains.buildServer.deployer.agent.SyncBuildProcessAdapter.start(SyncBuildProcessAdapter.java:58) at jetbrains.buildServer.agent.impl.buildStages.runnerStages.start.CallRunnerStage.doBuildStage(CallRunnerStage.java:58) at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor$1.callStage(RunnerStagesExecutor.java:25) at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor$1.callStage(RunnerStagesExecutor.java:18) at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.callRunStage(StagesExecutor.java:78) at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.doSt
7.x app server. My build setup is pretty vanilla Java application built with Ant and Ivy. Overall I like Jenkins and I'm trying to learn how to use it for continuous deployment, but the http://wrongnotes.blogspot.com/2015_05_01_archive.html lack of documentation explaining some of the plugins makes it extremely frustrating. This hopefully will explain some of the subtle configuration options better for these plugins. For this I've setup Jenkins with these plugins: GIT Client https://groups.google.com/d/topic/youtube-api-gdata/mjL-L4eu5zQ plugin GitBucket S3 Plugin I have two jobs. One builds my application which uses a post build step to Publish artifacts to S3 bucket. The second job is used to remotely deploy the artifacts from the error writing first job to the Tomcat 7.x server. The 2nd job is a parameterized build with the following configuration: Build selector for Copy Artifact name = BUILD_SELECTOR Execute Shell Command = rm -rf $WORKSPACE/build Copy S3 Artifact Project Name = MyApp Which Build = Specified by Build Parameter Parameter Name = BUILD_SELECTOR Artifact Copy = webappname-*.war Target Directory = $WORKSPACE/build Few things to note. BUILD_SELECTOR is the name of the environment variable error writing request that holds the user's selected build. The artifact to copy setting is not a path it's just a pattern used to select the artifact. I execute the rm command to clean up the artifacts between successive builds. The first problem I encountered was the 2nd job kept failing because it said there were not any artifacts from the 1st job. It is NOT documented anywhere that I could find, but once I went back to the 1st Job and marked the "Publish artifacts to S3 bucket" step as "Manage Artifacts". Once that was checked it finally recognized the artifacts and I got the following! Copied 1 artifact from "MyApp" build number 301 stored in S3 But the next problem was the deploy plugin kept failing with a very obtuse error. java.io.IOException: Error writing request body to server I found out that if I removed my application from the Tomcat 7.x webapps directory then it would actually deploy! But if I tried to redeploy it it failed with that obtuse error. I was deploying my app to Tomcat's ROOT context so my configuration looked like this: WAR/EAR = build/fuseanalytics-*.war Context = ROOT Container = Tomcat7x Manager User Name = none of your business Password = also none of your business Tomcat URL = http:/
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen