|
||||||||
|
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.
Given this is an exception originating from Windows networking, did you try Google?
E.g. http://blogs.msdn.com/b/sql_protocols/archive/2008/04/08/understanding-connection-forcibly-closed-by-remote-host-errors-caused-by-toe-chimney.aspx explains how to test for broken hardware.
http://social.msdn.microsoft.com/Forums/en-US/497175cf-a548-476e-ad19-feb938873032/exception-an-existing-connection-was-forcibly-closed-by-the-remote-host?forum=netfxnetcom indicates timeouts can cause this, which may be consistent with your bad line across the world (JENKINS-23868).