Intermittent connection reset errors when
We are encountering issues with our builds when connecting to our TFS system. We have a large number of errors similar to the ones below in the teamcity-vcs.log. The issue seems to occur frequently but is intermittent.
[2017-07-26 17:34:01,574] INFO [ical executor 4] - jetbrains.buildServer.VCS - Cannot load current state for VCS root "WindApp Main branch - TFS DirectConnect VCS Root" {instance id=3737, parent internal id=39, parent id=WindApp_WindAppMainBranchTfsDirectConnectVcsRoot, description: "tfs: http://xxxxxx/tfs/defaultcollection/ $/WindApp/Release/5.0.0.0"}: Connection reset
[2017-07-26 17:33:58,249] WARN [ical executor 9] - cs.ConnectionStateReporterImpl - Unable to collect changes for [DesignTools :: Release :: Bladed HardwareTest 2.1 Release {id=DesignTools_MaintenanceRelease_BladedHardwareTest21Release, internal id=bt308}]: jetbrains.buildServer.vcs.VcsRootVcsException: Error collecting changes for VCS repository '"BladedHardwareTest2.1Release" {instance id=3622, parent internal id=167, parent id=DesignTools_MaintenanceRelease_BladedHardwareTest21Release, description: "tfs: http://xxxxxx/tfs/defaultcollection/ $/BladedHardwareTest/Release/2.1.0.9"}'Connection reset
Has anyone encountered this issue before?
Although we have a single TFS instance we currently have 176 VCS roots configured and have a suspicion that this may be a problem. We can reduce this number but it will take some work so it would be good to know if this is the cause before we do this.
Please sign in to leave a comment.
Hi Stewart,
would it be possible to disable a good amount of VCS Roots during a period where the issue would happen consistently and see whether it reduces the impact or disappears?
That amount of VCS roots, if configured with the default value, will perform around 3 requests per second to the server, and those request can be heavy at times. That would also explain it being intermittent (some requests would be heavier and produce a larger workload than others), so trying to reduce the amount of VCS Roots, even if just for a test, might help. Increasing the checking for changes period might also help here if this is the issue at hand.
If you don't see any change in behavior with those changes, please send us the teamcity-server.log using the "Submit a request" button above.