Delayed Git updates and builds in TeamCity

Symptoms

TeamCity Server experiences delays in picking up the VCS (Version Control System) changes and starting corresponding builds. The delays could be significant, despite the default VCS check interval being set correctly. The server logs indicate warnings regarding limited thread pool resources and an inability to queue checking for changes due to queue capacity limits.

[2025-03-27 17:27:51,516]   WARN [anges monitor 1] -      jetbrains.buildServer.VCS - Failed to queue checking for changes for 449 VCS roots, will repeat next time. Last error: java.util.concurrent.RejectedExecutionException: Unable to put new task into the queue because maximum capacity is exceeded. Current queue size: 2000. Executor info: Thread factory "VCS Periodical executor" {corePoolSize=5; maxPoolSize=10; activeCount=10}
[2025-03-27 17:28:01,217]   WARN [anges monitor 1] -      jetbrains.buildServer.VCS - Failed to queue checking for changes for 451 VCS roots, will repeat next time. Last error: java.util.concurrent.RejectedExecutionException: Unable to put new task into the queue because maximum capacity is exceeded. Current queue size: 2000. Executor info: Thread factory "VCS Periodical executor" {corePoolSize=5; maxPoolSize=10; activeCount=10}

Cause

In some cases, the server may be configured with a strict limitation on the number of processes for the user running the TeamCity Server process. In that case, the server prevents spawning more Git processes under the same user to collect the changes, which causes the queue to grow in size and overflow.

Resolution

Increase the number of processes allowed to run simultaneously for the user running the TeamCity Server process.