java.io.IOException: remote file operation failed: /XXX at hudson.remoting.Channel@1fabae96:build-03: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2

Jenkins JIRA | Anton Lundin | 1 year ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    When a external tool re-wrote our poms, it added a xml header: {{<?xml version="1.0" encoding="UTF-8"?>}} before the <project> tag. This made maven-plugin blow up: {quote}ERROR: Failed to parse POMs java.io.IOException: remote file operation failed: /XXX at hudson.remoting.Channel@1fabae96:build-03: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2 at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.act(FilePath.java:969) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1364) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2691) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to build-03(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.FilePath.act(FilePath.java:980) ... 8 more Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1301) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2691) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){quote} I would have expected maven-plugin to handle that.

    Jenkins JIRA | 1 year ago | Anton Lundin
    java.io.IOException: remote file operation failed: /XXX at hudson.remoting.Channel@1fabae96:build-03: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2
  2. 0

    [TEST-FAILURE] 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing

    GitHub | 2 years ago | mesutcelik
    java.io.IOException: remote file operation failed: /scratch/jenkins/workspace/Hazelcast-3.x-nightly at hudson.remoting.Channel@41483db2:52df410d: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.arquillian:arquillian-bom:pom:1.0.3.Final in central (http://repo.cloudbees.com/content/repositories/central) @ line 83, column 25 [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 108, column 21 [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.protocol:arquillian-protocol-servlet:jar is missing. @ line 172, column 21
  3. 0

    FW: Build failed in Jenkins: okapi #1610

    Google Groups | 1 year ago | Yves Savourel
    java.io.IOException: remote file operation failed: <https://okapi.ci.cloudbees.com/job/okapi/ws/> at hudson.remoting.Channel@4473dab5:3c9bfac7: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact net.sf.okapi.connectors:build-connectors:pom:0.28-SNAPSHOT in cloudbees-private-snapshot-repository (https://repository-okapi.forge.cloudbees.com/snapshot) and 'parent.relativePath' points at wrong local POM @ line 4, column 13
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JIRA] (JENKINS-40903) Server Name Indication is not supported

    Google Groups | 2 months ago | bochenski.k...@gmail.com (JIRA)
    java.io.IOException: remote file operation failed: /home/acme/workspace/config-file-provider-plugin-maven at hudson.remoting.Channel@74a1dda5:IQ-61a8ac47b316: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: 12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for <readonly-mvnrepo.acme-internal.com> doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 13 12:37:13

    Root Cause Analysis

    1. hudson.remoting.ProxyException

      hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-parseable POM /XXX/pom.xml: expected start tag name and not < (position: START_DOCUMENT seen <<... @1:2) @ line 1, column 2

      at hudson.maven.MavenModuleSetBuild$PomParser.invoke()
    2. Hudson Maven Embedder
      MavenModuleSetBuild$PomParser.invoke
      1. hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1364)
      2. hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098)
      2 frames
    3. Hudson
      FilePath$FileCallableWrapper.call
      1. hudson.FilePath$FileCallableWrapper.call(FilePath.java:2691)
      1 frame
    4. Hudson :: Remoting Layer
      InterceptingExecutorService$1.call
      1. hudson.remoting.UserRequest.perform(UserRequest.java:121)
      2. hudson.remoting.UserRequest.perform(UserRequest.java:49)
      3. hudson.remoting.Request$2.run(Request.java:326)
      4. hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
      4 frames
    5. Java RT
      Thread.run
      1. java.util.concurrent.FutureTask.run(FutureTask.java:266)
      2. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      3. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      4. java.lang.Thread.run(Thread.java:745)
      4 frames