-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major
-
Component/s: core
-
Environment:Linux Ubuntu, Tomcat 6.x
I am submitting this as per Richard Mortimer's suggestion in https://issues.jenkins-ci.org/browse/JENKINS-12037?focusedCommentId=160224&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-160224
I've just posted on the mailing list (http://groups.google.com/group/jenkinsci-users/browse_frm/thread/7f96cdf57ffed6cf# ) - perhaps this is the same issue.
I have a multi-module project where I'm running the Maven goal "clean
surefire-report:report".
While the tests pass in our local machines, we're randomly having failures
in one of the modules in Jenkins. The console shows:
mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project cm-web: Error occurred in starting fork, check output in log cause : Error occurred in starting fork, check output in log Stack trace : org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project cm-web: Error occurred in starting fork, check output in log
We have Jenkins running in Tomcat and by running the build and inspecting
tomcat's log I see:
SEVERE: I/O error in channel Channel to Maven [java, -cp,
/usr/share/tomcat6/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/usr/share/tomcat6/.jenkins/tools/Jenkins_maven/boot/plexus-classworlds-2.4.jar,
org.jvnet.hudson.maven3.agent.Maven3Main,
/usr/share/tomcat6/.jenkins/tools/Jenkins_maven,
/usr/share/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.12.jar,
/usr/share/tomcat6/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar,
40284]
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1133)
Caused by: java.io.EOFException
at
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1127)
Restarting tomcat makes the problem go away (until it "randomly" appears again after a few days)
