-
Bug
-
Resolution: Not A Defect
-
Major
-
Ubuntu 10.04. Jenkins 1.527.
After upgrading from 1.461 to a recent 1.5xx release we started getting a rash of build failures that end with "ERROR: Maven JVM terminated unexpectedly with exit code 143". These are maven3 builds using the maven plugin. The builds will fail at different points. Switching the job to free-style succeeds every time.
In jenkins.log I get this error:
SEVERE: I/O error in channel Channel to Maven [java, -Xmx2048m, -cp, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.4/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.4, /var/run/jenkins/war/WEB-INF/lib/remoting-2.32.jar, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar, /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar, 35686]
hudson.remoting.DiagnosedStreamCorruptionException
with a large amount of backtrace interspersed with hex followed by
Caused by: java.io.StreamCorruptedException: invalid type code: 10
[JENKINS-19207] ERROR: Maven JVM terminated unexpectedly with exit code 143
Closing as there isn't any work to be done. I believe my issue was caused by upgrading from an older version to a much newer one and while this should normally work it's understandable that issues can occur. I ultimately solved the issue by doing a fresh install of the most recent version.
Eric Heydrick
added a comment - - edited Closing as there isn't any work to be done. I believe my issue was caused by upgrading from an older version to a much newer one and while this should normally work it's understandable that issues can occur. I ultimately solved the issue by doing a fresh install of the most recent version. 
I ended up doing a fresh installation and this error went away.