Please direct any build related queries to the builds@ mailing list. I had a look, 'Jenkins' consists of one master and lots of slaves. The Master is fine and did not need a restart. The error message indicated that the slave it was running on was the problem, in this case H10.
I looked and both the H10 and H11 slaves were running 4 concurrent builds at the time of the failures. Other projects running on H10 also had the same failures. I reduced the executors to run max 2 executors and this has helped. Thanks Gav… On 15/09/2014, at 7:11 AM, Mark Struberg <[email protected]> wrote: > Jenkins seems to be out of memory > > > On Monday, 15 September 2014, 0:58, Apache Jenkins Server > <[email protected]> wrote: > > > See <https://builds.apache.org/job/OpenWebBeans-trunk/1031/changes> > > Changes: > ... > [trunk] $ /home/jenkins/tools/java/latest1.6/bin/java -cp > /home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/classworlds.jar > hudson.maven.agent.Main /home/jenkins/tools/maven/apache-maven-2.2.1 > /home/jenkins/jenkins-slave/slave.jar > /home/jenkins/jenkins-slave/maven-interceptor.jar 39938 > /home/jenkins/jenkins-slave/maven2.1-interceptor.jar > # > # There is insufficient memory for the Java Runtime Environment to continue. > # Cannot create GC thread. Out of system resources. > # An error report file with more information is saved as: > # > <https://builds.apache.org/job/OpenWebBeans-trunk/ws/trunk/hs_err_pid6437.log> > [locks-and-latches] Releasing all the locks > [locks-and-latches] All the locks released > ERROR: Failed to launch Maven. Exit code = 1 > > >
