We updated Jenkins to 1.542 two days ago (from 1.514) and we're getting a lot of OOM errors. (info: Windows server 2008 R2, Jenkins JVM is jdk-x64-1.6 .0_26)
At first I did the simplest thing and increased the heap from 3G to 4.2G (and bumped up permgen). This didn't help so I started looking at threads via the Jenkins monitoring tool. It indicated the disk-usage plugin was hung. When you tried to view a page for a particularly large job, the page would "hang" and the stack trace showed the disk-usage plugin was to blame (or so I thought). Jira report with thread dump here: https://issues.jenkins-ci.org/browse/JENKINS-20876 We disabled the disk-usage plugin and restarted and now we can visit that job page. However, we still get OOM and lots of GCs in the logs at least once a day. The stack trace looks frighteningly similar to that from the disk-usage plugin. Here is an edited stack trace showing the methods common between the two OOM incidents: one during the disk-usage plugin and one after it was disabled: [lots of xstream methods snipped] hudson.XmlFile.unmarshal(XmlFile.java:165) hudson.model.Run.reload(Run.java:323) hudson.model.Run.<init>(Run.java:312) hudson.model.AbstractBuild.<init>(AbstractBuild.java:185) hudson.maven.AbstractMavenBuild.<init>(AbstractMavenBuild.java:54) hudson.maven.MavenModuleSetBuild.<init>(MavenModuleSetBuild.java:146) ... [JVM methods snipped] hudson.model.AbstractProject.loadBuild(AbstractProject.java:1155) hudson.model.AbstractProject$1.create(AbstractProject.java:342) hudson.model.AbstractProject$1.create(AbstractProject.java:340) hudson.model.RunMap.retrieve(RunMap.java:225) hudson.model.RunMap.retrieve(RunMap.java:59) jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:677) jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:660) jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:502) jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:536) hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:1077) hudson.maven.MavenBuild.getParentBuild(MavenBuild.java:165) hudson.maven.MavenBuild.getWhyKeepLog(MavenBuild.java:273) hudson.model.Run.isKeepLog(Run.java:572) ... It seems something in "core" Jenkins has changed and not for the better. Anyone seeing these issues? -tim -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
