• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core, maven-plugin
    • None

      Hi,

      After upgrading from 1.596 to 1.598 I am unable to run any Maven Jobs

      I am getting the following StackOverFlow Error.

      Parsing POMs
      ERROR: Failed to parse POMs
      java.io.IOException: remote file operation failed: /tr/j/jh2/workspace/Cannon_Test_maven at hudson.remoting.Channel@4d4d472e:01-Cannon2: java.io.IOException: Remote call on 01-Cannon2 failed
      	at hudson.FilePath.act(FilePath.java:985)
      	at hudson.FilePath.act(FilePath.java:967)
      	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:959)
      	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536)
      	at hudson.model.Run.execute(Run.java:1718)
      	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
      	at hudson.model.ResourceController.execute(ResourceController.java:89)
      	at hudson.model.Executor.run(Executor.java:240)
      Caused by: java.io.IOException: Remote call on 01-Cannon2 failed
      	at hudson.remoting.Channel.call(Channel.java:760)
      	at hudson.FilePath.act(FilePath.java:978)
      	... 8 more
      Caused by: java.lang.StackOverflowError
      	at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89)
      	at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72)
      	
      	at sun.reflect.GeneratedMethodAccessor20.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:40)
      	at com.sun.proxy.$Proxy30.lookup(Unknown Source)
      
      	at sun.reflect.GeneratedMethodAccessor20.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:40)
      	at com.sun.proxy.$Proxy30.lookup(Unknown Source)
      
      	...
      	1000 lines repeating
      	...
      
      	at com.sun.proxy.$Proxy30.lookup(Unknown Source)
      	at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at ......remote call to 01-Cannon2(Native Method)
      	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
      	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
      	at hudson.remoting.Channel.call(Channel.java:752)
      	... 9 more
      

        1. config.xml
          2 kB
          Daniel Beck

          [JENKINS-26601] StackOverflow Maven Job Parse Poms

          going to 1.597 has stopped the error

          Geoff Cummings added a comment - going to 1.597 has stopped the error

          Robert Hook added a comment -

          I have had similar issues today - upgraded from 1.597 to 1.598 and got OOM when maven was trying to deploy artefacts to our maven repository. Downgrading back to 1.597 sorted this out. Something has gone horribly wrong!

          Robert Hook added a comment - I have had similar issues today - upgraded from 1.597 to 1.598 and got OOM when maven was trying to deploy artefacts to our maven repository. Downgrading back to 1.597 sorted this out. Something has gone horribly wrong!

          Andreas Horst added a comment -

          Yes, I'm seeing this as well as JENKINS-26595.

          Andreas Horst added a comment - Yes, I'm seeing this as well as JENKINS-26595 .

          Daniel Beck added a comment -

          Does this only affect builds run on slaves, or also when building on master?

          Daniel Beck added a comment - Does this only affect builds run on slaves, or also when building on master?

          Also happens on master

          CentOS, JDK 1.7.0_55

          Geoff Cummings added a comment - Also happens on master CentOS, JDK 1.7.0_55

          Daniel Beck added a comment -

          I was unable to reproduce this with 1.598 on CentOS with OpenJDK 1.7, building on the master node, using a fresh Jenkins home only installing Git plugin.

          I tried with the Jenkins project at https://github.com/jenkinsci/jenkins and always got past the Parsing POMs state with both Maven Project plugin 1.1 and 1.2.


          Could someone please try to reproduce this issue using a pristine Jenkins home directory (as easy as

          export JENKINS_HOME=$HOME/JENKINS-26601-Test-Home ; java -jar jenkins.war --httpPort=9999

          ) and a publicly accessibly Maven project using SVN or Git, and post the instructions?

          Daniel Beck added a comment - I was unable to reproduce this with 1.598 on CentOS with OpenJDK 1.7, building on the master node, using a fresh Jenkins home only installing Git plugin. I tried with the Jenkins project at https://github.com/jenkinsci/jenkins and always got past the Parsing POMs state with both Maven Project plugin 1.1 and 1.2. Could someone please try to reproduce this issue using a pristine Jenkins home directory (as easy as export JENKINS_HOME=$HOME/JENKINS-26601-Test-Home ; java -jar jenkins.war --httpPort=9999 ) and a publicly accessibly Maven project using SVN or Git, and post the instructions?

          I get the same error on every maven build following upgrade. Error is:

          java.lang.StackOverflowError
          	at java.lang.Exception.<init>(Exception.java:102)
          	at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89)
          	at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72)
          	at sun.reflect.GeneratedMethodAccessor193.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:40)
          	at com.sun.proxy.$Proxy52.lookup(Unknown Source)
          	at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
          ...
          ...
                  at java.lang.reflect.Method.invoke(Method.java:606)
          	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)
          	at com.sun.proxy.$Proxy52.lookup(Unknown Source)
          	at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)
          
          

          Kevin Breidenbach added a comment - I get the same error on every maven build following upgrade. Error is: java.lang.StackOverflowError at java.lang.Exception.<init>(Exception.java:102) at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor193.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:40) at com.sun.proxy.$Proxy52.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) ... ... at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy52.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)

          Geoff Cummings added a comment - - edited

          It seem to happen if the pom uses a parent which is not in the workspace or the local maven repository.
          So using a basic pom which has the jenkins parent pom as its parent:

          • with 1.598 it gives the stack trace.
          • with 1.597 the parent pom downloaded from our nexus server, and builds ok.
          • 1.598 will build as the parent pom is available in the local maven repository.
          • 1.598 will fail if I delete the parent pom from the local maven repository, or update the job to use a maven repository local to the workspace which is empty.

          The basic pom can be found here: https://github.com/gcummings/JENKINS-26601

          1.598

          First time build. Skipping changelog.
          Parsing POMs
          FATAL: null
          java.lang.StackOverflowError
          	at java.lang.Exception.<init>(Exception.java:102)
          	at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89)
          	at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72)
          	at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source)
          
          

          1.597

          Parsing POMs
          Downloaded artifact http://xxxxxxxx/nexus/content/groups/public/org/jenkins-ci/main/pom/1.598/pom-1.598.pom
          Discovered a new module org.jenkins-ci.main:org.jenkins-ci.bug Jenkins Test Pom 26601
          Modules changed, recalculating dependency graph
          [workspace] $ java -Xmx4096m -XX:MaxPermSize=1024m -Dmaven.findbugs.jvmargs=-XX:MaxPermSize=1024m -Dmaven.test.failure.ignore=false -cp /xxxx/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.6.jar:/xxxx/tools/Maven/Maven_3.1.0/boot/plexus-classworlds-2.4.2.jar:/xxxx/tools/Maven/Maven_3.1.0/conf/logging jenkins.maven3.agent.Maven31Main /xxxx/tools/Maven/Maven_3.1.0 /xxxx/war/WEB-INF/lib/remoting-2.49.jar /xxxx/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.6.jar /xxxx/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.6.jar 52190
          <===[JENKINS REMOTING CAPACITY]===>channel started
          

          Geoff Cummings added a comment - - edited It seem to happen if the pom uses a parent which is not in the workspace or the local maven repository. So using a basic pom which has the jenkins parent pom as its parent: with 1.598 it gives the stack trace. with 1.597 the parent pom downloaded from our nexus server, and builds ok. 1.598 will build as the parent pom is available in the local maven repository. 1.598 will fail if I delete the parent pom from the local maven repository, or update the job to use a maven repository local to the workspace which is empty. The basic pom can be found here: https://github.com/gcummings/JENKINS-26601 1.598 First time build. Skipping changelog. Parsing POMs FATAL: null java.lang.StackOverflowError at java.lang.Exception.<init>(Exception.java:102) at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) 1.597 Parsing POMs Downloaded artifact http: //xxxxxxxx/nexus/content/groups/ public /org/jenkins-ci/main/pom/1.598/pom-1.598.pom Discovered a new module org.jenkins-ci.main:org.jenkins-ci.bug Jenkins Test Pom 26601 Modules changed, recalculating dependency graph [workspace] $ java -Xmx4096m -XX:MaxPermSize=1024m -Dmaven.findbugs.jvmargs=-XX:MaxPermSize=1024m -Dmaven.test.failure.ignore= false -cp /xxxx/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.6.jar:/xxxx/tools/Maven/Maven_3.1.0/boot/plexus-classworlds-2.4.2.jar:/xxxx/tools/Maven/Maven_3.1.0/conf/logging jenkins.maven3.agent.Maven31Main /xxxx/tools/Maven/Maven_3.1.0 /xxxx/war/WEB-INF/lib/remoting-2.49.jar /xxxx/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.6.jar /xxxx/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.6.jar 52190 <===[JENKINS REMOTING CAPACITY]===>channel started

          Robert Hook added a comment -

          Ok, that's a very useful analysis - I will be able to test that by forcing the parent pom into the local repo, and will report back when I have had a chance to do that.

          Robert Hook added a comment - Ok, that's a very useful analysis - I will be able to test that by forcing the parent pom into the local repo, and will report back when I have had a chance to do that.

          Daniel Beck added a comment -

          gcummings Thanks, that repo works for me (i.e. it's overflowing the stack). Investigating...

          Daniel Beck added a comment - gcummings Thanks, that repo works for me (i.e. it's overflowing the stack). Investigating...

          Daniel Beck added a comment -

          Daniel Beck added a comment - Caused by https://github.com/jenkinsci/jenkins/commit/3732aba5fe0d4a55847ae79496a81e5207f2acfc

          Daniel Beck added a comment -

          Attaching project that results in StackOverflowError on 1.600-SNAPSHOT, and regular failure to parse POMs on 1.600-SNAPSHOT with reverted Guice dependency. Needs Git plugin. Git is configured with JGit, Maven with one 3.2.2 installation.

          Daniel Beck added a comment - Attaching project that results in StackOverflowError on 1.600-SNAPSHOT, and regular failure to parse POMs on 1.600-SNAPSHOT with reverted Guice dependency. Needs Git plugin. Git is configured with JGit, Maven with one 3.2.2 installation.

          Jesse Glick added a comment -

          For the record, was from https://github.com/jenkinsci/jenkins/pull/1453. (For some reason GitHub is not mentioning this.)

          Jesse Glick added a comment - For the record, was from https://github.com/jenkinsci/jenkins/pull/1453 . (For some reason GitHub is not mentioning this.)

          Jesse Glick added a comment -

          maven-plugin also had its own dependency on Guice (the old one), for no apparent reason, since it would have inherited this from core anyway.

          Jesse Glick added a comment - maven-plugin also had its own dependency on Guice (the old one), for no apparent reason, since it would have inherited this from core anyway.

          Krzysztof K added a comment -

          After update to 1.598 I have the same problem.
          My stacktrace:

           > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
           > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
          Checking out Revision f91238b6db6c9a955f84150df33c2d617839984e (refs/remotes/origin/develop)
           > git config core.sparsecheckout # timeout=10
           > git checkout -f f91238b6db6c9a955f84150df33c2d617839984e
           > git rev-list f91238b6db6c9a955f84150df33c2d617839984e # timeout=10
          Parsing POMs
          FATAL: null
          java.lang.StackOverflowError
          	at java.lang.Exception.<init>(Exception.java:102)
          	at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89)
          	at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72)
          	at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          	at java.lang.reflect.Method.invoke(Method.java:483)
          	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)
          	at com.sun.proxy.$Proxy65.lookup(Unknown Source)
          	at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          	at java.lang.reflect.Method.invoke(Method.java:483)
          	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)
          	at com.sun.proxy.$Proxy65.lookup(Unknown Source)
          	at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          	at java.lang.reflect.Method.invoke(Method.java:483)
          	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)

          Krzysztof K added a comment - After update to 1.598 I have the same problem. My stacktrace: > git rev-parse refs/remotes/origin/develop^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10 Checking out Revision f91238b6db6c9a955f84150df33c2d617839984e (refs/remotes/origin/develop) > git config core.sparsecheckout # timeout=10 > git checkout -f f91238b6db6c9a955f84150df33c2d617839984e > git rev-list f91238b6db6c9a955f84150df33c2d617839984e # timeout=10 Parsing POMs FATAL: null java.lang.StackOverflowError at java.lang.Exception.<init>(Exception.java:102) at java.lang.ReflectiveOperationException.<init>(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy65.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy65.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)

          Jesse Glick added a comment -

          An easier way to reproduce the stack trace: edit maven-plugin/pom.xml to use the altered dependency, then mvn -Dtest=hudson.maven.RedeployPublisherTest#testTarGzMaven3 test. <version>4.0-beta4</version> also fails. Including or omitting <classifier>no_aop</classifier> makes no difference, so this just seems like a Guice regression.

          Jesse Glick added a comment - An easier way to reproduce the stack trace: edit maven-plugin/pom.xml to use the altered dependency, then mvn -Dtest=hudson.maven.RedeployPublisherTest#testTarGzMaven3 test . <version>4.0-beta4</version> also fails. Including or omitting <classifier>no_aop</classifier> makes no difference, so this just seems like a Guice regression.

          Jesse Glick added a comment -

          Unable to reproduce with the sample project in a dev build because I just get java.lang.NoSuchMethodError: org.eclipse.aether.spi.connector.ArtifactDownload.setListener(Lorg/eclipse/aether/transfer/TransferListener;)Lorg/eclipse/aether/spi/connector/ArtifactDownload; regardless of which version of Maven I use, even after upgrading the Maven plugin. I feel like this is filed somewhere already, but I could not find it.

          Jesse Glick added a comment - Unable to reproduce with the sample project in a dev build because I just get java.lang.NoSuchMethodError: org.eclipse.aether.spi.connector.ArtifactDownload.setListener(Lorg/eclipse/aether/transfer/TransferListener;)Lorg/eclipse/aether/spi/connector/ArtifactDownload; regardless of which version of Maven I use, even after upgrading the Maven plugin. I feel like this is filed somewhere already, but I could not find it.

          Code changed in jenkins
          User: Jesse Glick
          Path:
          changelog.html
          pom.xml
          http://jenkins-ci.org/commit/jenkins/00c858d403ab1f7747de0b9ce80e1eef921c41b3
          Log:
          [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/00c858d403ab1f7747de0b9ce80e1eef921c41b3 Log: [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899 .

          Olivier Lamy added a comment -

          Olivier Lamy added a comment - see comments https://github.com/google/guice/issues/899

          dogfood added a comment -

          Integrated in jenkins_main_trunk #3954
          [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899. (Revision 00c858d403ab1f7747de0b9ce80e1eef921c41b3)

          Result = SUCCESS
          jesse glick : 00c858d403ab1f7747de0b9ce80e1eef921c41b3
          Files :

          • pom.xml
          • changelog.html

          dogfood added a comment - Integrated in jenkins_main_trunk #3954 [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899 . (Revision 00c858d403ab1f7747de0b9ce80e1eef921c41b3) Result = SUCCESS jesse glick : 00c858d403ab1f7747de0b9ce80e1eef921c41b3 Files : pom.xml changelog.html

          Any idea when this will be released?

          Samuel Gabriel added a comment - Any idea when this will be released?

          Daniel Beck added a comment -

          http://jenkins-ci.org/changelog ("Upcoming Changes")

          Daniel Beck added a comment - http://jenkins-ci.org/changelog ("Upcoming Changes")

          Jesse Glick added a comment -

          BTW I am happy to merge to the rc branch to get it into 1.599, but I need someone to first confirm that the fix works. As previously noted, I encountered an unrelated error first that blocked me from testing it.

          Jesse Glick added a comment - BTW I am happy to merge to the rc branch to get it into 1.599, but I need someone to first confirm that the fix works. As previously noted, I encountered an unrelated error first that blocked me from testing it.

          Daniel Beck added a comment -

          Seems to work.

          Rather than use gcummings' test repo, I built a simple Jenkins plugin in a project configured to use a local repo in the workspace (which always gets cleaned up), like the attached config.

          • 1.600-SNAPSHOT build with Guice 4.0-beta5: StackOverflowError
          • 1.600-SNAPSHOT build with Guice 4.0-beta/no_aop: Maven first downloads the internet, then I get an HPI.
          • 1.600-SNAPSHOT from Jan 28 with Guice 4.0-beta: Maven first downloads the internet again, then I get an HPI.

          So it seems to resolve this issue.

          Daniel Beck added a comment - Seems to work. Rather than use gcummings ' test repo, I built a simple Jenkins plugin in a project configured to use a local repo in the workspace (which always gets cleaned up), like the attached config. 1.600-SNAPSHOT build with Guice 4.0-beta5: StackOverflowError 1.600-SNAPSHOT build with Guice 4.0-beta/no_aop: Maven first downloads the internet, then I get an HPI. 1.600-SNAPSHOT from Jan 28 with Guice 4.0-beta: Maven first downloads the internet again, then I get an HPI. So it seems to resolve this issue.

          Code changed in jenkins
          User: Jesse Glick
          Path:
          changelog.html
          pom.xml
          http://jenkins-ci.org/commit/jenkins/a0942b88346d66770336daec7bf82063163e8001
          Log:
          [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899.

          (cherry picked from commit 00c858d403ab1f7747de0b9ce80e1eef921c41b3 into 1.599 rc)

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/a0942b88346d66770336daec7bf82063163e8001 Log: [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899 . (cherry picked from commit 00c858d403ab1f7747de0b9ce80e1eef921c41b3 into 1.599 rc)

          dogfood added a comment -

          Integrated in jenkins_main_trunk #3961
          [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899. (Revision a0942b88346d66770336daec7bf82063163e8001)

          Result = SUCCESS
          jesse glick : a0942b88346d66770336daec7bf82063163e8001
          Files :

          • pom.xml
          • changelog.html

          dogfood added a comment - Integrated in jenkins_main_trunk #3961 [FIXED JENKINS-26601] Partly reverting #1453 to avoid hitting https://github.com/google/guice/issues/899 . (Revision a0942b88346d66770336daec7bf82063163e8001) Result = SUCCESS jesse glick : a0942b88346d66770336daec7bf82063163e8001 Files : pom.xml changelog.html

          How difficult it is to create a test case for this bug?

          Rade Martinovic added a comment - How difficult it is to create a test case for this bug?

          DI2E SysAdmin added a comment -

          Will the fix be included in 1.599? And when is that expected to be released?

          DI2E SysAdmin added a comment - Will the fix be included in 1.599? And when is that expected to be released?

          Shalom Kazaz added a comment -

          example project attached tc-jenkins.zip

          when parent pom is in remote repo jenkins fails.
          the project:
          two modules referencing a parent deployed in artifactory. a root pom as reactor.

          jenkins 1.598
          simple maven job.
          local maven 3.2.5 home, but same happens with auto install.
          checks out ./project
          maven build step: clean install
          settings.xml containing artifactory mirror in jenkins home .m2/settings.xml
          parent deployed to artifactory

          when run on master:
          Parsing POMs
          FATAL: null
          java.lang.StackOverflowError
          at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72)

          build the jenkins workspace manually with mvn clean install succeeds and downloads the parent from artifactory.
          now the jenkins job works because the parent is in the local repo.
          remove the settings.xml from jenkins home .m2/settings.xml , jenkins job fails with same exception although the parent is still in the local repo.
          supplly Maven settings.xml and Global settings.xml configured with artifactory mirror, by config file plugin. jenkins job succeeds again.
          delete the parent from the local repo. jenkins job fails again.
          if I add on this 'Resolve artifacts from Artifactory' the jenkins job is stuck.

          same thing when configuring jenkins to Use private Maven repository

          downgrade to 1.597 all is working again

          Shalom Kazaz added a comment - example project attached tc-jenkins.zip when parent pom is in remote repo jenkins fails. the project: two modules referencing a parent deployed in artifactory. a root pom as reactor. jenkins 1.598 simple maven job. local maven 3.2.5 home, but same happens with auto install. checks out ./project maven build step: clean install settings.xml containing artifactory mirror in jenkins home .m2/settings.xml parent deployed to artifactory when run on master: Parsing POMs FATAL: null java.lang.StackOverflowError at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72) build the jenkins workspace manually with mvn clean install succeeds and downloads the parent from artifactory. now the jenkins job works because the parent is in the local repo. remove the settings.xml from jenkins home .m2/settings.xml , jenkins job fails with same exception although the parent is still in the local repo. supplly Maven settings.xml and Global settings.xml configured with artifactory mirror, by config file plugin. jenkins job succeeds again. delete the parent from the local repo. jenkins job fails again. if I add on this 'Resolve artifacts from Artifactory' the jenkins job is stuck. same thing when configuring jenkins to Use private Maven repository downgrade to 1.597 all is working again

          Jesse Glick added a comment -

          The fix should be in 1.599.

          Jesse Glick added a comment - The fix should be in 1.599.

          DI2E SysAdmin added a comment - - edited

          Can someone confirm that this fix is included in 1.599?

          DI2E SysAdmin added a comment - - edited Can someone confirm that this fix is included in 1.599?

          Thomas Suckow added a comment -

          I no longer see stack overflow in 1.599

          Thomas Suckow added a comment - I no longer see stack overflow in 1.599

          Andreas Horst added a comment -

          Yes, confirmed. Everything looking pretty stable over here.

          Andreas Horst added a comment - Yes, confirmed. Everything looking pretty stable over here.

          Petteri Kauko added a comment -

          When will this be fixed in the LTS? I ran into this after installing 1.580.3 but I don't see anything in the upcoming changes for LTS.

          Petteri Kauko added a comment - When will this be fixed in the LTS? I ran into this after installing 1.580.3 but I don't see anything in the upcoming changes for LTS.

          DI2E SysAdmin added a comment -

          Thank you for the verification.

          DI2E SysAdmin added a comment - Thank you for the verification.

            jglick Jesse Glick
            gcummings Geoff Cummings
            Votes:
            12 Vote for this issue
            Watchers:
            36 Start watching this issue

              Created:
              Updated:
              Resolved: