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

StackOverflowError parsing Maven POM

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: core, maven-plugin
    • Labels:
      None
    • Environment:
      os.name Windows Server 2012 R2 (64-bit)
      java.vendor Oracle Corporation
      java.version 1.8.0_66
      Jenkins ver. 2.32.2
      maven-plugin 2.13
    • Similar Issues:

      Description

      The offending job was working fine until I updated Jenkins to 2.32.1; the problem still manifests after having further updated to Jenkins ver. 2.32.2. I have other Jenkins jobs which run fine on the same master+slave (both running on the same machine) and can't discern any significant differences in their configuration.

      The stack trace is:
      Parsing POMs
      ERROR: Failed to parse POMs
      java.io.IOException: remote file operation failed: C:\jenkins\workspace\object-api\build-objectapi-codegen\codegen at hudson.remoting.Channel@a7fd77:Channel to /10.100.87.126: java.io.IOException: Remote call on Channel to /10.100.87.126 failed
      at hudson.FilePath.act(FilePath.java:992)
      at hudson.FilePath.act(FilePath.java:974)
      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:534)
      at hudson.model.Run.execute(Run.java:1728)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:404)
      Caused by: java.io.IOException: Remote call on Channel to /10.100.87.126 failed
      at hudson.remoting.Channel.call(Channel.java:830)
      at hudson.FilePath.act(FilePath.java:985)
      ... 8 more
      Caused by: java.lang.StackOverflowError
      at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
      at com.sun.proxy.$Proxy30.lookup(Unknown Source)
      at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
      at com.sun.proxy.$Proxy30.lookup(Unknown Source)
      ... unbounded recursion ...
      at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
      at ......remote call to Channel to /10.100.87.126(Native Method)
      at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
      at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
      at hudson.remoting.Channel.call(Channel.java:822)
      ... 9 more

      The stack trace is near identical to JENKINS-26601, which was reported against Jenkins 1.598 and resolved on 2015/Jan/28.

        Attachments

          Issue Links

            Activity

            Hide
            girishkg Girish KG added a comment -

            This issue is still exist and can be re-produced in:

            Jenkins-2.46.2 and Maven Integration plugin v2.17

            Show
            girishkg Girish KG added a comment - This issue is still exist and can be re-produced in: Jenkins-2.46.2 and Maven Integration plugin v2.17
            Hide
            aheritier Arnaud Héritier added a comment -

            Added in 2.15.1 changelog

            Show
            aheritier Arnaud Héritier added a comment - Added in 2.15.1 changelog
            Hide
            aheritier Arnaud Héritier added a comment - - edited

            The sum-up:

            • OK with Jenkins < 2.32.1 (not sure which) and the Maven plug-in which came with that version
            • KO with Jenkins 2.32.1 and Maven plugin 2.13
            • KO with Jenkins 2.32.2 and Maven plugin 2.13
            • OK with Jenkins 2.32.2 and Maven plugin 2.13 + workaround: specifying explicit values for Source Code Management > Subversion > Modules > Local module directory.
            • OK with Jenkins 2.32.2 and Maven plugin 2.15.1
            • KO with Jenkins 2.41 and Maven plugin 2.9
            • OK with Jenkins 2.41 and Maven plugin 2.15.1

            Upgrade to Guice Final 4.0 was done in Jenkins 2.28

            Show
            aheritier Arnaud Héritier added a comment - - edited The sum-up: OK with Jenkins < 2.32.1 (not sure which) and the Maven plug-in which came with that version KO with Jenkins 2.32.1 and Maven plugin 2.13 KO with Jenkins 2.32.2 and Maven plugin 2.13 OK with Jenkins 2.32.2 and Maven plugin 2.13 + workaround: specifying explicit values for Source Code Management > Subversion > Modules > Local module directory. OK with Jenkins 2.32.2 and Maven plugin 2.15.1 KO with Jenkins 2.41 and Maven plugin 2.9 OK with Jenkins 2.41 and Maven plugin 2.15.1 Upgrade to Guice Final 4.0 was done in Jenkins 2.28
            Hide
            aheritier Arnaud Héritier added a comment -

            thx for you feedback Sébastien Gollion
            Maven plugin users don't hesitate to comment here like Sébastien if you have also this error. It may help us to better identify the the change/issue even if it is fixed by the latest version of the plugin (from my POV it smells the issue related to the guice/sisu update in core and maven plugin cc Oleg Nenashev)

            Show
            aheritier Arnaud Héritier added a comment - thx for you feedback Sébastien Gollion Maven plugin users don't hesitate to comment here like Sébastien if you have also this error. It may help us to better identify the the change/issue even if it is fixed by the latest version of the plugin (from my POV it smells the issue related to the guice/sisu update in core and maven plugin cc Oleg Nenashev )
            Hide
            adrianp Adrian Price added a comment - - edited

            Last week when I upgraded to Maven Integration Plugin 2.14 I also upgraded all the other plug-ins, which included Subversion Plugin 2.7.1. But before I got a chance to test that combination I was called off to do some other work, then this morning I saw the comments about 2.15.1 being available so I once again upgraded all plug-ins, which fixed the problem and obviated the need for the workaround.

            The sum-up should be:

            • OK with Jenkins < 2.32.1 (not sure which) and the Maven plug-in which came with that version
            • KO with Jenkins 2.32.1 and Maven plugin 2.13
            • KO with Jenkins 2.32.2 and Maven plugin 2.13
            • OK with Jenkins 2.32.2 and Maven plugin 2.13 + workaround: specifying explicit values for Source Code Management > Subversion > Modules > Local module directory.
            • OK with Jenkins 2.32.2 and Maven plugin 2.15.1
            Show
            adrianp Adrian Price added a comment - - edited Last week when I upgraded to Maven Integration Plugin 2.14 I also upgraded all the other plug-ins, which included Subversion Plugin 2.7.1. But before I got a chance to test that combination I was called off to do some other work, then this morning I saw the comments about 2.15.1 being available so I once again upgraded all plug-ins, which fixed the problem and obviated the need for the workaround. The sum-up should be: OK with Jenkins < 2.32.1 (not sure which) and the Maven plug-in which came with that version KO with Jenkins 2.32.1 and Maven plugin 2.13 KO with Jenkins 2.32.2 and Maven plugin 2.13 OK with Jenkins 2.32.2 and Maven plugin 2.13 + workaround: specifying explicit values for Source Code Management > Subversion > Modules > Local module directory. OK with Jenkins 2.32.2 and Maven plugin 2.15.1

              People

              • Assignee:
                aheritier Arnaud Héritier
                Reporter:
                adrianp Adrian Price
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: