The thread dumps show a large number of the following thread, which is indicative of the loss of the NIO selector thread. This will make the master believe that it has all the TCP connections to slaves alive, except no bytes will be ever read:

"TCP slave agent connection handler #109 with /ipaddr.47.66:49583 / waiting for hudson.remoting.Channel@27a41103:ci-61b-mac109" Id=1726 Group=main TIMED_WAITING on hudson.remoting.UserRequest@790457f7
	at java.lang.Object.wait(Native Method)
	-  waiting on hudson.remoting.UserRequest@790457f7
	at hudson.remoting.Request.call(Request.java:146)
	at hudson.remoting.Channel.call(Channel.java:739)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:449)
	at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120)
	at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63)
	at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57)
	at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31)
	at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:157)

Based on this, I think you are seeing JENKINS-22932. The fix to that adds better error diagnostics, and there's a recent separate fix for a related but different problem that will result in the same symptom at JENKINS-24050. I'm going to close this as a duplicate, but please see my last comment to JENKINS-24050, run the later version of Jenkins, and look for additional error messages on the master.

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.

Reply via email to