|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14332) Repeated channel/timeout e... [email protected] (JIRA)
- [JIRA] (JENKINS-14332) Repeated channel/time... [email protected] (JIRA)
- [JIRA] (JENKINS-14332) Repeated channel/time... [email protected] (JIRA)
- [JIRA] (JENKINS-14332) Repeated channel/time... [email protected] (JIRA)
- [JIRA] (JENKINS-14332) Repeated channel/time... [email protected] (JIRA)
- [JIRA] (JENKINS-14332) Repeated channel/time... [email protected] (JIRA)

The message looks ok to me. There is 360 seconds difference between the two timestamps which would be consistent with a timeout.
However I have a feeling that this is due to some additional changes that Koshuke made when he merged my remoting pull-3. See
https://github.com/jenkinsci/remoting/commit/aceaf5c038e8179723f9a83be6f994f37e7cfa46
Previously the TimeoutException (ping failed) message would only have been observed if a TimeoutException was received. Now the message will be logged when the loop ends. Maybe there is a real timeout/delay here that was previously hidden.
One other note. The while(remaining>0) gets evaluated after a timeout exception but remaining will only get recalculated on the next loop so there will be an extra pass around the loop.