|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This could be related to the problem we have with hanging slaves.
The problem we had was that Jenkins noticed that the program it is running has ended and thus thinks that the program has a bug where it won't send the eof tag. Due to this it wants to write back a message about a wiki post.
""String msg = "Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information";
Throwable e = new Exception().fillInStackTrace();
LOGGER.log(Level.WARNING,msg,e);""
But at this point the logger connection is deadlocked and the job will hang. To prevent the hanging we've patched our version of Jenkins with https://github.com/jenkinsci/jenkins/pull/665.