Part of the problem is that when we stopped the Jenkins Windows service, the wrapper stopped, but the Java process continued (later saw some errors about failure to terminate the process). So when we started the service again, we effectively had *two* copies of Jenkins running, both independently polling.
On Friday, May 15, 2015 at 3:58:09 PM UTC-4, Trinition wrote: > > Our Windows Jenkins 1.613 server is presently going out of control with > polling. > > We have about 50 jobs configured. Each is set for either "H/5 * * * *" or > "H/10 * * * *". Yet as soon as we start out server, dozens of polling's > are kicked off (we have no slaves; our polling is done via a command line > process, so we can see it in Task Manager). I can't tell if it's only > dozens instead of 50 because it's just choking under the load, or that's > the natural "H" distribution. > > What is the behavior of Jenkins when the server starts up and it has ~50 > "H/..." jobs? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3d92479b-61ec-4d71-a7e2-34fb0219af72%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
