Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-10540

Maven build aborted without cause

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core, maven-plugin
    • Labels:
      None
    • Environment:
      Linux CentOS 5.5 x64
      Jenkins 1.418
      Maven 3.0.3
    • Similar Issues:

      Description

      We have an incremental multi module maven build set up, that behaves correctly when running the build on the top level project.

      However, when drilling into a specific module within the project, and running the build from there, the build aborts immediately, with the build's console output showing:

      Started by user anonymous
      ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro
      $ /opt/apps/java_home/bin/java -Xmx512m -cp /opt/apps/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/opt/apps/maven_home/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /opt/apps/maven_home /opt/apps/web/tomcat-8080/webapps/jenkins/WEB-INF/lib/remoting-1.418.jar /opt/apps/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 51579
      <===[JENKINS REMOTING CAPACITY]===>channel started
      Finished: ABORTED

      On enabling the jenkins system logger, I can see the below when executing the build:

      01-Aug-2011 17:32:46 hudson.remoting.Channel$ReaderThread run
      SEVERE: I/O error in channel Channel to Maven [/opt/apps/java_home/bin/java, -Xmx512m, -cp, /opt/apps/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/opt/apps/maven_home/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /opt/apps/maven_home, /opt/apps/web/tomcat-8080/webapps/jenkins/WEB-INF/lib/remoting-1.418.jar, /opt/apps/jenkins_home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar, 51579]
      java.io.IOException: Unexpected termination of the channel
      at hudson.remoting.Channel$ReaderThread.run(Channel.java:1025)
      Caused by: java.io.EOFException
      at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
      at hudson.remoting.Channel$ReaderThread.run(Channel.java:1019)
      01-Aug-2011 17:32:46 hudson.remoting.Channel$ReaderThread run
      FINE: Received Response[retVal=hudson.remoting.UserResponse@242aeeeb,exception=null]
      01-Aug-2011 17:32:46 hudson.remoting.Channel send
      FINE: Send Response[retVal=hudson.remoting.RemoteClassLoader$ClassFile@5264a7cb,exception=null]
      01-Aug-2011 17:32:46 hudson.remoting.Channel$ReaderThread run
      FINE: Received RPCRequest(2,fetch2)
      01-Aug-2011 17:32:46 hudson.remoting.Channel send
      FINE: Send UserRequest:hudson.maven.ProcessCache$GetSystemProperties@1ece1486

      There are no pending changes on the module being built, but I would expect Jenkins to run a build for this module when explicitly requested to do so.

        Attachments

          Activity

          Hide
          sraf S Raf added a comment -

          I've played around with this some more, and looks like the issue doesn't occur with Maven 2.2.1 - but is reproducible with Maven 3.0.3.

          Also, it affects all multi-module maven builds, regardless of whether they're set up as incremental.

          Show
          sraf S Raf added a comment - I've played around with this some more, and looks like the issue doesn't occur with Maven 2.2.1 - but is reproducible with Maven 3.0.3. Also, it affects all multi-module maven builds, regardless of whether they're set up as incremental.
          Hide
          taeric Josh Berry added a comment -

          This looks like the underlying problem for JENKINS-10406. That is, I originally hit the issue described in that description, and found that trying maven2 works.

          Show
          taeric Josh Berry added a comment - This looks like the underlying problem for JENKINS-10406 . That is, I originally hit the issue described in that description, and found that trying maven2 works.
          Hide
          slash Bernhard Trummer added a comment -

          I can reproduce exactly the same behavior on our Jenkins instances (1.431 - 1.433).
          Falling back to Maven 2.x however is not an option for us, because our poms require Maven 3(.0.3).

          Some background information:
          For our actual projects, this issue doesn't matter at all, because the incremental build feature is sufficient and I don't need to trigger the build of a dedicated module here.
          But we also have integration test projects in a multi-module pom structure. Roughly spoken: one parent pom and one test project for every component.
          So my idea is to create one Jenkins job for the parent pom, which is then executed once in the night via a cron trigger. However, it would also be nice to be able to manually trigger a single test project (means: a "module"). The build buttons in the "modules" section are exactly what I need in this case, but unfortunately it doesn't work.

          Of course it would be possible to create a Jenkins job for every single test project and put them all into a job view. But since we are talking about 20-30 projects here, the resulting job config duplication is a "no go" for my point of view...

          Show
          slash Bernhard Trummer added a comment - I can reproduce exactly the same behavior on our Jenkins instances (1.431 - 1.433). Falling back to Maven 2.x however is not an option for us, because our poms require Maven 3(.0.3). Some background information: For our actual projects, this issue doesn't matter at all, because the incremental build feature is sufficient and I don't need to trigger the build of a dedicated module here. But we also have integration test projects in a multi-module pom structure. Roughly spoken: one parent pom and one test project for every component. So my idea is to create one Jenkins job for the parent pom, which is then executed once in the night via a cron trigger. However, it would also be nice to be able to manually trigger a single test project (means: a "module"). The build buttons in the "modules" section are exactly what I need in this case, but unfortunately it doesn't work. Of course it would be possible to create a Jenkins job for every single test project and put them all into a job view. But since we are talking about 20-30 projects here, the resulting job config duplication is a "no go" for my point of view...
          Hide
          sniglom Adam H added a comment - - edited

          Seeing similar error message on Jenkins 1.532 and Maven 3.0.5:

          Nov 22, 2013 8:29:23 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE:
          I/O error in channel Channel to Maven
          [java,
          -Dmaven.repo.basedir=file:///folder/mvn.repo/,
          -cp,
          /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/usr/local/share/java/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar,
          org.jvnet.hudson.maven3.agent.Maven3Main,
          /usr/local/share/java/apache-maven-3.0.5,
          /jenkins/hostname/servername/.jenkins/war/WEB-INF/lib/remoting-2.32.jar,
          /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar,
          /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar,
          41611]
          java.io.IOException: Unexpected termination of the channel at
          hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by:
          java.io.EOFException at
          java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at
          java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1316) at
          java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at
          hudson.remoting.Command.readFrom(Command.java:92) at
          hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at
          hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

          Show
          sniglom Adam H added a comment - - edited Seeing similar error message on Jenkins 1.532 and Maven 3.0.5: Nov 22, 2013 8:29:23 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Channel to Maven [java, -Dmaven.repo.basedir= file:///folder/mvn.repo/ , -cp, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/usr/local/share/java/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /usr/local/share/java/apache-maven-3.0.5, /jenkins/hostname/servername/.jenkins/war/WEB-INF/lib/remoting-2.32.jar, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar, 41611] java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1316) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
          Hide
          tknerr Torben Knerr added a comment - - edited

          Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds.

          Adam H Bernhard Trummer Josh Berry S Raf did you ever find a suitable workaround?

          Show
          tknerr Torben Knerr added a comment - - edited Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds. Adam H Bernhard Trummer Josh Berry S Raf did you ever find a suitable workaround?
          Hide
          taeric Josh Berry added a comment -

          For us, as annoying as it felt, simply giving up on the parallel option worked.

          Show
          taeric Josh Berry added a comment - For us, as annoying as it felt, simply giving up on the parallel option worked.
          Hide
          tknerr Torben Knerr added a comment -

          Tried adding a dummy post build step in the hope that the build status would be derived from the last build step, but that did not help either...

          Show
          tknerr Torben Knerr added a comment - Tried adding a dummy post build step in the hope that the build status would be derived from the last build step, but that did not help either...
          Hide
          kattamine Greg Domjan added a comment -

          Still a problem in Jenkins 1.656

          Job output looks like

          Started by user X
          Building on master in workspace c:\Jenkins-BuildArea\Incremental\modulesAll
          Updating https://svn/svn/trunk at revision '2016-05-12T14:40:00.133 +0530'
          At revision 40034
          
          No changes for https://svn/svn/trunk since the previous build
          Parsing POMs
          Triggering com.netIQ.IAM.SecureLogin:binariesbuild
          [WARNINGS] Parsing warnings in console log with parser MSBuild
          [WARNINGS] Parsing warnings in console log with parser Java Compiler (javac)
          [WARNINGS] Parsing warnings in console log with parser Maven
          [WARNINGS] Computing warning deltas based on reference build #5
          No emails were triggered.
          Finished: SUCCESS
          

          jenkins.err.log has

          INFO: Trunk binary modules #5 main build action completed: SUCCESS
          May 12, 2016 2:17:18 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run
          SEVERE: I/O error in channel Channel to Maven [C:\Program Files\Java\jdk1.7.0_07/bin/java, -cp, C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.7.jar;C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.3\boot\plexus-classworlds-2.5.2.jar;C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.3/conf/logging, jenkins.maven3.agent.Maven32Main, C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.3, C:\Jenkins\war\WEB-INF\lib\remoting-2.56.jar, C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-interceptor-1.7.jar, C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.7.jar, 60912]
          java.net.SocketException: Connection reset
          	at java.net.SocketInputStream.read(Unknown Source)
          	at java.net.SocketInputStream.read(Unknown Source)
          	at java.io.FilterInputStream.read(Unknown Source)
          	at java.io.BufferedInputStream.fill(Unknown Source)
          	at java.io.BufferedInputStream.read(Unknown Source)
          	at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82)
          	at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72)
          	at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
          	at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
          	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
          	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
          
          May 12, 2016 2:17:18 PM hudson.model.Run execute
          INFO: Trunk binary modules/com:binariesbuild #5 main build action completed: NOT_BUILT
          
          Show
          kattamine Greg Domjan added a comment - Still a problem in Jenkins 1.656 Job output looks like Started by user X Building on master in workspace c:\Jenkins-BuildArea\Incremental\modulesAll Updating https://svn/svn/trunk at revision '2016-05-12T14:40:00.133 +0530' At revision 40034 No changes for https://svn/svn/trunk since the previous build Parsing POMs Triggering com.netIQ.IAM.SecureLogin:binariesbuild [WARNINGS] Parsing warnings in console log with parser MSBuild [WARNINGS] Parsing warnings in console log with parser Java Compiler (javac) [WARNINGS] Parsing warnings in console log with parser Maven [WARNINGS] Computing warning deltas based on reference build #5 No emails were triggered. Finished: SUCCESS jenkins.err.log has INFO: Trunk binary modules #5 main build action completed: SUCCESS May 12, 2016 2:17:18 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Channel to Maven [C:\Program Files\Java\jdk1.7.0_07/bin/java, -cp, C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-agent-1.7.jar;C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.3\boot\plexus-classworlds-2.5.2.jar;C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.3/conf/logging, jenkins.maven3.agent.Maven32Main, C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.3, C:\Jenkins\war\WEB-INF\lib\remoting-2.56.jar, C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven32-interceptor-1.7.jar, C:\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.7.jar, 60912] java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) May 12, 2016 2:17:18 PM hudson.model.Run execute INFO: Trunk binary modules/com:binariesbuild #5 main build action completed: NOT_BUILT
          Hide
          julien_may Julien May added a comment -
          Show
          julien_may Julien May added a comment - IMHO this is related to https://issues.jenkins-ci.org/browse/JENKINS-13171

            People

            • Assignee:
              Unassigned
              Reporter:
              sraf S Raf
            • Votes:
              10 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated: