|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [JIRA] (JENKINS-12235) FATAL, Unable to del... pukhal...@bpc.ru (JIRA)
- [JIRA] (JENKINS-12235) FATAL, Unable t... pukhal...@bpc.ru (JIRA)
- [JIRA] (JENKINS-12235) FATAL, Unable t... pukhal...@bpc.ru (JIRA)
- [JIRA] (JENKINS-12235) FATAL, Unable t... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-12235) FATAL, Unable t... dogf...@java.net (JIRA)
Jenkins 1.489 here and it happens too. The master and slave are RHEL5.8.
The task runs for 15 minutes in my case. The output is being spewn and setting neither ClientAliveInterval and ClientAliveCountMax nor TCPKeepAlive helped.
It started to happen after i've joined two "execute shell" steps into one. The sockets, processes numbers are well within limits
The slave appears to exit (crash?). In the slave log there is:
...
Evacuated stdout
Slave successfully connected and online
ERROR: Connection terminated
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
Probably it's somewhere in the JVM entrails? Now i'll try to play with different JVMs and settings as it's a blocking issue for me.