|
||||||||
|
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'm getting this problem as well. It happens to my Windows VMs about 2/3 times. When there is a queue, new jobs can start right after the socket exception happens; could it be a timeout that has been set too strict? I think it might also be related to the high network traffic that Jenkins is creating (see JENKINS-24040).