Is that not more a question of changing the MAVEN_OPTS for the jobs in question to give them more memory -Xmx*BigAmount*m
AFAIK, Hudson always forks a new JVM for all jobs... even the Crazy Maven2 project type (as oposed to freestyle Maven2 builds which are not crazy at all) -Stephen On Fri, Sep 19, 2008 at 8:41 AM, Benjamin Bentmann < [EMAIL PROTECTED]> wrote: > Hi, > > the last four builds of our CI job "plugins-CI-with-maven-2.0.x" failed > with > > FATAL: GC overhead limit exceeded > java.lang.OutOfMemoryError: GC overhead limit exceeded > > The related CI jobs "plugins-CI-with-maven-2.1.x" and > "plugins-IT-with-maven-2.0.x" seem to suffer the same fate. > > Does the machine have some more memory available that could go into Hudson? > > > Benjamin > > > [0] https://ci.sonatype.org/job/plugins-CI-with-maven-2.0.x/458/console > [1] https://ci.sonatype.org/job/plugins-CI-with-maven-2.0.x/459/console > [2] https://ci.sonatype.org/job/plugins-CI-with-maven-2.0.x/460/console > [3] https://ci.sonatype.org/job/plugins-CI-with-maven-2.0.x/461/console > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
