-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Debian 8.3 64bit
OpenJDK 1.8.0_72
Jenkins 1.650 running on Tomcat 8
Every plugin up to date
Whenever I enable the either the "Publish Checkstyle analysis result", "Publish FindBugs analysis result" or the "Scan workspace for open tasks" option, I get the following Exception:
{{[CHECKSTYLE] Parsing file /var/lib/jenkins/jobs/Hello-World-ANY/workspace/target/checkstyle-result.xml
[CHECKSTYLE] Successfully parsed file /var/lib/jenkins/jobs/Hello-World-ANY/workspace/target/checkstyle-result.xml of module HelloWorld with 10 unique warnings and 0 duplicates.
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(ObjectInputStream.java:2830)
at java.io.ObjectInputStream.readInt(ObjectInputStream.java:972)
at com.google.common.collect.Serialization.readCount(Serialization.java:50)
at com.google.common.collect.HashMultimap.readObject(HashMultimap.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1058)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1900)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1707)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
at hudson.remoting.UserRequest.deserialize(UserRequest.java:184)
at hudson.remoting.UserRequest.perform(UserRequest.java:98)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18)
at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
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 channel(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
at hudson.remoting.Channel.call(Channel.java:781)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
at com.sun.proxy.$Proxy5.execute(Unknown Source)
at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:207)
at hudson.plugins.analysis.core.HealthAwareReporter.registerResultsOnMaster(HealthAwareReporter.java:364)
at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:355)
at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634)
at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:615)
at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:308)
at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:104)
at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131)
at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.jvnet.hudson.maven3.launcher.Maven32Launcher.main(Maven32Launcher.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
at jenkins.maven3.agent.Maven32Main.launch(Maven32Main.java:186)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:136)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
at hudson.remoting.UserRequest.perform(UserRequest.java:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
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)}}
- duplicates
-
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
[JENKINS-33210] EOFException when using Static Analysis Collector
Lucas Layman
added a comment - I am having the same issue. Maven 3.3.9. 
Vlad Lapadatescu
added a comment - I'm having the same issue as well whenever I set any of the following plug-ins to publish results:
- Findbugs
- Checkstyle
- PMD
- TaskScanner
Using:
- Ubuntu 16.04.1 LTS
- Jenkins 2.7.4
- Maven 3.3.9
- jdk1.8.0_102
- all plugins are at the latest version.
I did not have this issue on Windows
Can you please help?
I'd be happy to provide more details if needed.
Vlad Lapadatescu
added a comment - I'm having the same issue as well whenever I set any of the following plug-ins to publish results:
Findbugs
Checkstyle
PMD
TaskScanner
Using:
Ubuntu 16.04.1 LTS
Jenkins 2.7.4
Maven 3.3.9
jdk1.8.0_102
all plugins are at the latest version.
I did not have this issue on Windows
Can you please help?
I'd be happy to provide more details if needed. 
tzafrir
added a comment - I had the same problem.
Fixed it by setting up a new maven installation in Global settings.
If jenkins was directed to use maven installed on my laptop, I got this error.
But when I changed the settings to download new installation of maven from apache, and set it up and /opt it worked just fine.
tzafrir
added a comment - I had the same problem.
Fixed it by setting up a new maven installation in Global settings.
If jenkins was directed to use maven installed on my laptop, I got this error.
But when I changed the settings to download new installation of maven from apache, and set it up and /opt it worked just fine. Vlad Lapadatescu
added a comment - Thank you!
This actually solved my problem as well! I would rather re-open this issue. On ubuntu 16, most people will install maven is
sudo apt-get install maven
However, this has some issues. The command line:
mvn pmd:pmd
works (of course assuming you have configured the plugin correctly in pom.xml and other caveats).
This however fails inside Jenkins with the dreaded EOF message. The correct way then to install maven on Ubuntu 16 then would be:
wget http://www-eu.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz sudo tar xvfvz apache-maven-3.3.9-bin.tar.gz -C /opt sudo ln -s /opt/apache-maven-3.3.9 /opt/maven sudo sh -c 'echo MAVEN_HOME=/opt/maven >> /etc/environment' sudo ln -s /opt/maven/bin/mvn /usr/bin/mvn
or an equivalent to above.
If the issue cannot be re-opened, it might be a good idea to at-least warn users on this. Just my 2 cents 
Seshagiri Sriram
added a comment - - edited I would rather re-open this issue. On ubuntu 16, most people will install maven is
sudo apt-get install maven
However, this has some issues. The command line:
mvn pmd:pmd
works (of course assuming you have configured the plugin correctly in pom.xml and other caveats).
This however fails inside Jenkins with the dreaded EOF message. The correct way then to install maven on Ubuntu 16 then would be:
wget http: //www-eu.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz
sudo tar xvfvz apache-maven-3.3.9-bin.tar.gz -C /opt
sudo ln -s /opt/apache-maven-3.3.9 /opt/maven
sudo sh -c 'echo MAVEN_HOME=/opt/maven >> /etc/environment'
sudo ln -s /opt/maven/bin/mvn /usr/bin/mvn
or an equivalent to above.
If the issue cannot be re-opened, it might be a good idea to at-least warn users on this. Just my 2 cents
Joel Bartley
added a comment - I'm seeing the same error when I use maven 3.5.0 instead of 3.3.9. Going back to 3.3.9 fixes it for me, but I'd like to think there will be an upgrade path to eventually use the latest maven version with jenkins.
Joel Bartley
added a comment - I'm seeing the same error when I use maven 3.5.0 instead of 3.3.9. Going back to 3.3.9 fixes it for me, but I'd like to think there will be an upgrade path to eventually use the latest maven version with jenkins. This bug still exists when using anything but a maven 3.3.x version. Switching projects between maven 3.5.x and 3.3.9 make this bug appear and disappear. It is very annoying as it stops us from moving a number of projects to a newer maven version.
This bug i fixed with the Static Analyzer plugin 1.93 that has been released a few days ago.
(And it is also proof that, if you really want a bug fixed, you need to fix it yourself. )
Hello,
I can reproduce this error. We are using labels to group our nodes. The next step on a successful build is
If I change now the label to use other nodes, the build will fail with the mentioned IO error in the description. I think the report does not get handled between different nodes?