Cargo Java.io.ioexception Error Writing Request Body To Server
Contents |
Support
Ant Tomcat Error Writing Request Body To Server
Search GitHub This repository Watch 18 Star 25 Fork 17
Httpurlconnection Error Writing Request Body To Server
JetBrains/teamcity-deployer-plugin Code Issues 20 Pull requests 1 Projects 0 Pulse Graphs New issue Deploy to Tomcat
Ant Error Writing Request Body To Server
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 Milestone No milestone Assignees caused by: java.io.ioexception: error writing request body to server 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.doStages(StagesExecutor.java:37) at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor.doStages(RunnerStagesExecutor.java:18) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.RunnerContextExecutor.callRunnerStages(RunnerContextExecutor.java:43) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor.processNextStep(StepExecutor.java:25) at jetbrains.buildServer.agent.impl.buildStages.startStages.st
- 15th for workshops, presentations and java.io.ioexception: error writing to server all things Jenkins Learn more Export Tools JenkinsJENKINS-24096Jenkins Tomcat deploymet errorLog In ExportXMLWordPrintable Details Type: Bug Status: Open Priority: Major Resolution: Unresolved Component/s: deploy-plugin Labels: https://github.com/JetBrains/teamcity-deployer-plugin/issues/54 deploy jenkins tomcat Environment: Jenkins 1.552 Deploy Plugin 1.9 Similar Issues: Show Description I have been using Jenkins for quite some time for Continuous integration with my Java projects. Recently I https://issues.jenkins-ci.org/browse/JENKINS-24096 tried the Jenkins Deploy Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin) to deploy my war file on tomcat 7. However, I am unable to do so as I am getting the following error: Bug Stack Trace Deploying C:\Program Files (x86)\Jenkins\jobs\MY_PROJS\workspace\target\projs.war to container Tomcat 7.x Remote [C:\Program Files (x86)\Jenkins\jobs\MY_PROJS\workspace\target\projs.war] is not deployed. Doing a fresh deployment. Deploying [C:\Program Files (x86)\Jenkins\jobs\MY_PROJS\workspace\target\projs.war] ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception org.codehaus.cargo.container.ContainerException: Failed to deploy [C:\Program Files (x86)\Jenkins\jobs\MY_PROJS\workspace\target\projs.war] at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:115) at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:187) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuil
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 lack of documentation explaining some of http://wrongnotes.blogspot.com/2015_05_01_archive.html 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 plugin GitBucket S3 Plugin I have two jobs. One https://developer.jboss.org/thread/252956 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 first job to the Tomcat 7.x server. The 2nd job is error writing 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 that holds the user's selected build. The artifact to copy setting is not a path it's just a error writing request 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://somehost So the clue was the following logging written out in the console output: "is not deployed." Copied 1 artifact from "MyApp" build number 301 stored in S3 Deploying /var/lib/jenkins/workspace/MyApp/build/myapp-1.0-301.war to container Tomcat 7.x Remote [/var/li
not work correctly without it enabled. Please turn JavaScript back on and reload this page. All Places > ModeShape > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 2 Replies Latest reply on Mar 13, 2015 7:13 PM by Rafael Trestini "Error writing request body to server" on upload ~50Mb file Rafael Trestini Mar 12, 2015 2:37 PM Hi guys,I'm starting to evaluate Modeshape 4.1.0-Final with Wildfly 8.2. My installation is completely default with no modification in any configuration file, except those mentioned in this guide [1]. I'm not an expert neither with Wildfly nor Modeshape, but I couldn't find any reference to this error.I'm just trying to upload a file with ~50Mb.Assuming:a remote installation in a Centos 7 linux boxjava 1.8.0_20using CMIS with AtomPubthe client code: public void saveFile(String folderName, String originalName, byte[] fileContent){ Map properties = new HashMap(); properties.put(PropertyIds.OBJECT_TYPE_ID, "cmis:unversioned-document"); properties.put(PropertyIds.NAME, originalName); InputStream fileStream = new ByteArrayInputStream(fileContent); String mimetype = // guessMimeType(fileContent); "application/zip"; ContentStream contentStream = new ContentStreamImpl( originalName, BigInteger.valueOf(fileContent.length), mimetype, fileStream); Folder folder = null; if( folderName == null ){ folder = this.client.getSession().getRootFolder(); } else { folder = (Folder) this.client.getSession().getObjectByPath(folderName); } Document newDoc = folder.createDocument( properties, contentStream, VersioningState.NONE); } The error raised is the following:org.apache.chemistry.opencmis.commons.exceptions.CmisConnectionException: Cannot access "http://192.168.10.79:8080/modeshape-cmis/atom/artifacts/children?id=ef2822b9-bc1f-42aa-891c-bd753da1c0a8&versioningState=none": Error writing request body to server at org.apache.chemistry.opencmis.client.bindings.spi.http.DefaultHttpInvoker.invoke(DefaultHttpInvoker.java:230) at org.apache.chemistry.opencmis.client.bindings.spi.http.DefaultHttpInvoker.invokePOST(DefaultHttpInvoker.java:65) at org.apache.chemistry.opencmis.clie