Hi Team, I'm managing a Jenkins instance (version 1.480.2) which holds 263 jobs from different projects. These jobs are configured to run on every SCM change.
All the builds turn on slaves and the Master is used only to hold the Tomcat 6 server where Jenkins is running. I thought that this would let Jenkins be more comfortable. But my assumption went wrong beause recenlty, each morning I have to restart Tomcat because: - It becomes very very slow - Non of the jobs run because the server is overcharged from SCM polling And sometimes the server went down due to many sever errors like "java.lang.OutOfMemoryError: Java heap space" I'm wondering if it's normal that Jenkins acts that way when it exceeds a certain limit of jobs, or should I change my Tomcat configuration in order to support this ? I'll be very thankful for any suggestion that may be helpful. Regards, Mehdi -- 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. For more options, visit https://groups.google.com/groups/opt_out.
