Jenkins 1.489 here and it happens too.
The master and slave are RHEL5.8.
The task runs for quite a time, alright. But there is output 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, moreso (we run a series of tests) it always happens around the test number, say, N±3 which adds weight to the timeout hypothesis.

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.

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

Reply via email to