|
||||||||
|
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.
What's likely happening is that the NIO selector thread has died on the master, which uses NioChannelHub.abortAll() to terminate all the JNLP connections. It's consistent with the observation that the problem persists until Jenkins restarts. If anyone can take a thread dump on the master when Jenkins is in this state, we can verify this by checking if the said thread is listed or not.
When NIO selector thread is killed, it leaves a message in the Jenkins log. I'd like you to look for it, so that we can see why the NIO selector thread is killed. The reconnecting slaves failing to get through is red herring.