If you're a git user, instead of increasing the numebr of threads, you might consider revisiting your polling definition. I was polling git once a minute from multiple jobs until I discovered the "Git polling must die" blog posting from Kohsuke. See http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ If you still need to increase the number of threads, http://jenkins.361315.n4.nabble.com/Polling-hung-td1310838.html seems to hint that adjusting the number of threads is done from the Jenkins configuration page, but the option may only be available if you have more than 10 jobs defined. I don't see it on my Jenkins instance that has more than 10 jobs defined, but there is an entry "SCM Polling" whose help text says "If you use SCM polling to trigger a new build for a large number of projects, you may want to limit the number of concurrent polling activities to avoid overloading the server. Setting a positive number sets the upper bound to the number of concurrent polling. Leaving the field empty will make it unbounded" Mark Waite
>________________________________ > From: Michael Latiolais <mikelatiol...@gmail.com> >To: jenkinsci-users@googlegroups.com >Sent: Tuesday, January 15, 2013 2:27 PM >Subject: Question abou increasing number of threads in Jenkins > > >I had a Jenkins server present this message today: >"There are more SCM polling activities scheduled than handled, so the threads >are not keeping up with the demands. Check if your polling is hanging, and/or >increase the number of threads if necessary." > >How do I go about increasing the number of threads? > >
