|
||||||||
|
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/d/optout.

I've seen the same issue on a Windows slave running a self-built version of 1.577-SNAPSHOT. The slave error log suggests that slave saw a connection reset but when it reconnected the master thought the slave was still connected and connection retries failed.
After 3 retries at restarting the windows service restarter gave up and unfortuntely I didn't attempt to reconnect until after I had restarted the master over 12 hours later.
The equivalent part of the master's logs are as follows (only the first restart included here but the others are equivalent).
The master log does not show any evidence of the slave connection being broken in the 12 hours before the master restart.
If the master is not detecting that the connection has closed then it will still think that the slave is connected and will refuse re-connections as seen.
Sadly I didn't get a stacktrace of the master's threads to see if any threads were blocked anywhere.