-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
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
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.
- depends on
-
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
[JENKINS-41697] StackOverflowError parsing Maven POM
Adrian Price
created issue -
danielbeck until I updated Jenkins to 2.32.1
Doesn't mean anything unless you mention what version you were running before.
Unfortunately, in updating from 2.32.1 to 2.32.2, any evidence as to the version that was installed prior to 2.32.1 was destroyed, because 2.32.2 overwrote jenkins.war.bak. I can't find any kind of installation history in the UI under 'Manage Jenkins', nor does there appear to be any kind of installation log file, nor is there any mention of 2.32.* in any of the error logs. It's a shame that Jenkins does not record these version bumps anywhere given that this is apparently vital diagnostic information.
I seem to recall doing another such update a few months ago, but there I'm not aware of any way to discover exactly when that was. Sorry I can't be any more precise than this.
aheritier I'd prefer not to downgrade if at all possible, as this can lead to loss of configuration information and/or plug-in compatibility problems.
Adrian Price
added a comment - - edited danielbeck until I updated Jenkins to 2.32.1
Doesn't mean anything unless you mention what version you were running before.
Unfortunately, in updating from 2.32.1 to 2.32.2, any evidence as to the version that was installed prior to 2.32.1 was destroyed, because 2.32.2 overwrote jenkins.war.bak. I can't find any kind of installation history in the UI under 'Manage Jenkins', nor does there appear to be any kind of installation log file, nor is there any mention of 2.32.* in any of the error logs. It's a shame that Jenkins does not record these version bumps anywhere given that this is apparently vital diagnostic information.
I seem to recall doing another such update a few months ago, but there I'm not aware of any way to discover exactly when that was. Sorry I can't be any more precise than this.
aheritier I'd prefer not to downgrade if at all possible, as this can lead to loss of configuration information and/or plug-in compatibility problems. adrianp I was talking about the maven plugin . You are using the version 2.13 and 2.14 is out for a several months. 2.15 is in progress
2.15.1 is out. If you can tell me if you have the same issue with it ...
| Link |
New:
This issue depends on |
I hope it's not related to our upgrade to guice but it is strange it was already in 2.32.1
https://github.com/jenkinsci/jenkins/commit/f64a2231396ad8de1d164bce20dc31751714b607
https://github.com/google/guice/issues/899 was closed but I don't understand if the fix was done in guice 4 final or sisu cc jglick
Perhaps the upgrade/cleanup of the maven-plugin 2.15 could help here
I don't understand if the fix was done in guice 4 final or sisu
Neither—the bug was on the Jenkins side, using an old component.
thanks jglick
Let us know adrianp if you have the problem with Jenkins 2.32.1 and maven plugin 2.15.1 please
Doesn't mean anything unless you mention what version you were running before.