java.io.IOException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • When performing a m2release it performs everything correctly, and then the artifactory plugin tries to deploy the next snapshot artifacts, and I get the stack trace that follows. As you can see the m2release completes successful. It correctly deploys the next snapshots jar, and fails on the pom. I traced it to the ArtifactDeployer and ensured that the source pom file exists on the hudson server running the release. The wording of the IO error is a little odd. Makes me think that the IO error is wrapped. I verified this by breaking on IOExceptions and it threw quite a few. That is when I gave up and decided to file a ticket. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 31 seconds [INFO] Finished at: Thu Jul 01 11:06:20 EDT 2010 [INFO] Final Memory: 17M/41M [INFO] ------------------------------------------------------------------------ channel stopped Deploying artifacts to https://repository.its.yale.edu/maven2 Deploying artifacts of module: edu.yale.its:yale-junit Deploying artifact: https://repository.its.yale.edu/maven2/lib-snapshots-public/edu/yale/its/yale-junit/1.0.14-SNAPSHOT/yale-junit-1.0.14-SNAPSHOT.jar Deploying artifact: https://repository.its.yale.edu/maven2/lib-snapshots-public/edu/yale/its/yale-junit/1.0.14-SNAPSHOT/yale-junit-1.0.14-SNAPSHOT.pom ERROR: Failed to deploy file: Not Found java.io.IOException: Failed to deploy file: Not Found at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:310) at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:234) at org.jfrog.hudson.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:99) at org.jfrog.hudson.ArtifactsDeployer.deploy(ArtifactsDeployer.java:64) at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:598) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1280) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:127) Finished: FAILURE
    via by jvalerio,
  • When performing a m2release it performs everything correctly, and then the artifactory plugin tries to deploy the next snapshot artifacts, and I get the stack trace that follows. As you can see the m2release completes successful. It correctly deploys the next snapshots jar, and fails on the pom. I traced it to the ArtifactDeployer and ensured that the source pom file exists on the hudson server running the release. The wording of the IO error is a little odd. Makes me think that the IO error is wrapped. I verified this by breaking on IOExceptions and it threw quite a few. That is when I gave up and decided to file a ticket. [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 31 seconds [INFO] Finished at: Thu Jul 01 11:06:20 EDT 2010 [INFO] Final Memory: 17M/41M [INFO] ------------------------------------------------------------------------ channel stopped Deploying artifacts to https://repository.its.yale.edu/maven2 Deploying artifacts of module: edu.yale.its:yale-junit Deploying artifact: https://repository.its.yale.edu/maven2/lib-snapshots-public/edu/yale/its/yale-junit/1.0.14-SNAPSHOT/yale-junit-1.0.14-SNAPSHOT.jar Deploying artifact: https://repository.its.yale.edu/maven2/lib-snapshots-public/edu/yale/its/yale-junit/1.0.14-SNAPSHOT/yale-junit-1.0.14-SNAPSHOT.pom ERROR: Failed to deploy file: Not Found java.io.IOException: Failed to deploy file: Not Found at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:310) at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:234) at org.jfrog.hudson.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:99) at org.jfrog.hudson.ArtifactsDeployer.deploy(ArtifactsDeployer.java:64) at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:598) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1280) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:127) Finished: FAILURE
    via by jvalerio,
  • Currently running into an issue with how the artifactory plugin is working when performing a release in Hudson using the maven release plugin (http://wiki.hudson-ci.org/display/HUDSON/M2+Release+Plugin). The problem occurs at the end of the release when it is trying to publish the new snapshot to artifactory. For some reason the artifactory plugin things it is working with the old snapshot version and won't let the artifact be put into artifactory. Here is the relevant log entry on hudson. {code} Deploying artifacts to http://artifactory-repo:8081 Deploying artifacts of module: groupid:artifactid Deploying artifact: http://artifactory-repo:8081/local-snapshots/groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom ERROR: Failed to deploy file: HTTP response code: 404. HTTP response message: The target deployment path 'groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom' does not match the POM's expected path prefix 'groupid/artifactid/0.0.8-SNAPSHOT'. Please verify your POM content for correctness and make sure the source path is a valid Maven 2 repository root path. java.io.IOException: Failed to deploy file: HTTP response code: 404. HTTP response message: The target deployment path 'groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom' does not match the POM's expected path prefix 'groupid/artifactid/0.0.8-SNAPSHOT'. Please verify your POM content for correctness and make sure the source path is a valid Maven 2 repository root path. at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:441) at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:374) at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:275) at org.jfrog.hudson.maven2.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:125) at org.jfrog.hudson.maven2.ArtifactsDeployer.deploy(ArtifactsDeployer.java:89) at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:177) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:595) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1303) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:293) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:137) Skipping sonar analysis due to bad build status FAILURE Finished: FAILURE {code} artifactory-repo, groupid, and artifactid are replacements for non-public domain information.
    via by Shawn Clark,
  • Currently running into an issue with how the artifactory plugin is working when performing a release in Hudson using the maven release plugin (http://wiki.hudson-ci.org/display/HUDSON/M2+Release+Plugin). The problem occurs at the end of the release when it is trying to publish the new snapshot to artifactory. For some reason the artifactory plugin things it is working with the old snapshot version and won't let the artifact be put into artifactory. Here is the relevant log entry on hudson. {code} Deploying artifacts to http://artifactory-repo:8081 Deploying artifacts of module: groupid:artifactid Deploying artifact: http://artifactory-repo:8081/local-snapshots/groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom ERROR: Failed to deploy file: HTTP response code: 404. HTTP response message: The target deployment path 'groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom' does not match the POM's expected path prefix 'groupid/artifactid/0.0.8-SNAPSHOT'. Please verify your POM content for correctness and make sure the source path is a valid Maven 2 repository root path. java.io.IOException: Failed to deploy file: HTTP response code: 404. HTTP response message: The target deployment path 'groupid/artifactid/0.0.7-SNAPSHOT/artifactid-0.0.7-SNAPSHOT.pom' does not match the POM's expected path prefix 'groupid/artifactid/0.0.8-SNAPSHOT'. Please verify your POM content for correctness and make sure the source path is a valid Maven 2 repository root path. at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:441) at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:374) at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:275) at org.jfrog.hudson.maven2.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:125) at org.jfrog.hudson.maven2.ArtifactsDeployer.deploy(ArtifactsDeployer.java:89) at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:177) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:595) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1303) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:293) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:137) Skipping sonar analysis due to bad build status FAILURE Finished: FAILURE {code} artifactory-repo, groupid, and artifactid are replacements for non-public domain information.
    via by Shawn Clark,
  • When deploying artifacts and the artifacts checksum to Artifactory, the artifact itself must be uploaded before it's checksum. Otherwise Artifactory will return with an Error 404 and consequently failing the job: 05:57:24 Deploying artifact: http://artifactory:8081/artifactory/repository/artifact.rpm.md5 05:57:24 ERROR: remote file operation failed: /root/workspace/job at hudson.remoting.Channel@2c03b560:hostname 05:57:24 java.io.IOException: remote file operation failed: /root/workspace/job at hudson.remoting.Channel@2c03b560:hostname 05:57:24 at hudson.FilePath.act(FilePath.java:916) 05:57:24 at hudson.FilePath.act(FilePath.java:893) 05:57:24 at org.jfrog.hudson.generic.GenericArtifactsDeployer.deploy(GenericArtifactsDeployer.java:82) 05:57:24 at org.jfrog.hudson.generic.ArtifactoryGenericConfigurator$1.tearDown(ArtifactoryGenericConfigurator.java:276) 05:57:24 at hudson.model.Build$BuildExecution.doRun(Build.java:170) 05:57:24 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 05:57:24 at hudson.model.Run.execute(Run.java:1706) 05:57:24 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 05:57:24 at hudson.model.ResourceController.execute(ResourceController.java:88) 05:57:24 at hudson.model.Executor.run(Executor.java:232) 05:57:24 Caused by: java.io.IOException: Failed to deploy file: HTTP response code: 404. HTTP response message: Not Found 05:57:24 at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:652) 05:57:24 at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:527) 05:57:24 at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:302) 05:57:24 at org.jfrog.hudson.generic.GenericArtifactsDeployer$FilesDeployerCallable.deploy(GenericArtifactsDeployer.java:182) 05:57:24 at org.jfrog.hudson.generic.GenericArtifactsDeployer$FilesDeployerCallable.invoke(GenericArtifactsDeployer.java:154) 05:57:24 at org.jfrog.hudson.generic.GenericArtifactsDeployer$FilesDeployerCallable.invoke(GenericArtifactsDeployer.java:122) 05:57:24 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2474) 05:57:24 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 05:57:24 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 05:57:24 at hudson.remoting.Request$2.run(Request.java:328) 05:57:24 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 05:57:24 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 05:57:24 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 05:57:24 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) 05:57:24 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 05:57:24 at java.lang.Thread.run(Thread.java:701) Versus the proper order returns a successful deploy and successful job: 05:40:14 Deploying artifact: http://artifactory:8081/artifactory/repository/artifact.rpm 05:40:38 Deploying artifact: http://artifactory:8081/artifactory/repository/artifact.rpm.md5 05:40:38 Deploying build info to: http://artifactory:8081/artifactory/api/build 05:40:39 Finished: SUCCESS Same Jenkins, Artifactory, Build Host, Code Base, and git checksum in both instances. The only difference was artifact deployment order. Either force checksum files to be uploaded last, or allow the user to specify priority order of artifact deployment.
    via by Daniel Dewey,
  • Hi! I'm not sure I'm posting to right project. Anyway... We are using teamcity plugin to deploy our artifacts. Today we found our builds starts to fail with stack like this: {noformat} java.lang.RuntimeException: Error deploying artifact: /opt/teamcity/buildAgent/work/48555869d50ef6eb/<path_to_project>/target/<project>.war. Skipping deployment of remaining artifacts (if any) and build info. java.lang.RuntimeException: Error deploying artifact: /opt/teamcity/buildAgent/work/48555869d50ef6eb/<path_to_project>/target/<project>.war. Skipping deployment of remaining artifacts (if any) and build info. at org.jfrog.teamcity.agent.listener.AgentListenerBuildInfoHelper.runnerFinished(AgentListenerBuildInfoHelper.java:157) at org.jfrog.teamcity.agent.ArtifactoryAgentListener.runnerFinished(ArtifactoryAgentListener.java:108) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at jetbrains.buildServer.util.EventDispatcher.dispatch(EventDispatcher.java:115) at jetbrains.buildServer.util.EventDispatcher$2.invoke(EventDispatcher.java:67) at $Proxy8.runnerFinished(Unknown Source) at jetbrains.buildServer.agent.impl.buildStages.runnerStages.finish.FireRunnerFinishedFStage.doFinishStage(FireRunnerFinishedFStage.java:29) at jetbrains.buildServer.agent.impl.buildStages.RunnerFinishStagesExecutor.runFinishStage(RunnerFinishStagesExecutor.java:32) at jetbrains.buildServer.agent.impl.buildStages.RunnerFinishStagesExecutor.doBuildFinishStages(RunnerFinishStagesExecutor.java:23) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.RunnerContextExecutor.safeCallFinishStages(RunnerContextExecutor.java:65) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.RunnerContextExecutor.callRunnerStages(RunnerContextExecutor.java:56) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor.doProcessNextStep(StepExecutor.java:89) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor.processNextStep(StepExecutor.java:44) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.ForEachBuildRunnerStage.doBuildStage(ForEachBuildRunnerStage.java:77) at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor$1.callStage(BuildStagesExecutor.java:31) at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor$1.callStage(BuildStagesExecutor.java:24) 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.BuildStagesExecutor.doStages(BuildStagesExecutor.java:24) at jetbrains.buildServer.agent.impl.BuildRunAction.doStages(BuildRunAction.java:70) at jetbrains.buildServer.agent.impl.BuildRunAction.runBuild(BuildRunAction.java:50) at jetbrains.buildServer.agent.impl.BuildAgentImpl.doActualBuild(BuildAgentImpl.java:247) at jetbrains.buildServer.agent.impl.BuildAgentImpl.access$100(BuildAgentImpl.java:48) at jetbrains.buildServer.agent.impl.BuildAgentImpl$1.run(BuildAgentImpl.java:220) at java.lang.Thread.run(Thread.java:722) Caused by: java.io.IOException: Failed to deploy file: HTTP response code: 413. HTTP response message: Request Entity Too Large at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:642) at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:517) at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:292) at org.jfrog.teamcity.agent.listener.AgentListenerBuildInfoHelper.runnerFinished(AgentListenerBuildInfoHelper.java:155) ... 27 more {noformat} War file is about 64M. We already tried to tweak jetty settings (i.e requestBufferSize/headerBufferSize) but without any hope. Maybe we are missing something? Could Artifactory somehow restrict file size?
    via by Vsevolod Minkov,
    • java.io.IOException: Failed to deploy file: Not Found at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:310) at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:234) at org.jfrog.hudson.ArtifactsDeployer.deployArtifact(ArtifactsDeployer.java:99) at org.jfrog.hudson.ArtifactsDeployer.deploy(ArtifactsDeployer.java:64) at org.jfrog.hudson.ArtifactoryRedeployPublisher.perform(ArtifactoryRedeployPublisher.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:598) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1280) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:127)

    Users with the same issue

    Unknown visitor
    Unknown visitor1 times, last one,