|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I attached debug/troubleshooting patch on top of Remoting-2.17, modifying Request.java file, to this ticket.
We have had this in use for a week now, without problems. I created it for debugging/troubleshooting purposes, which is why it is kind of messy.
For us, it seems to stop the problem from occuring, based on log output. And by that I mean, the (apparently) spurious InterruptedExceptions, which aborted builds in a bad way, no longer happen at all, while other presumably normal InterruptedExceptions do get logged... So this might be some kind of timing/race condition issue, where changing the code will change the behavior and hide the bug.