Hi,
On 09/03/2012 11:47, Deniz Acay wrote:
Hi everyone,
There is a problem I have been struggling with Jenkins. I tried
different CI servers but none of them offers the same features Jenkins
has, so I want to use it.
I have a small Rackspace CloudServer instance with 256MB RAM and running
Jenkins with Apache Tomcat 7 in that server. Using Maven 2 and Git
plugins of Jenkins.
The problem is, either Maven JVM exits with the code 137 (when forking
is enabled) or I get mysterious crashes. I know that the 256MB of RAM
may not be enough for Jenkins; but the thing is: even when I am running
Jenkins, I can build the project via command line in a short period of
time. My project involves some heavy servers, and generally the test are
failing with Jenkins.
I suspect that the operating system kernel is short on virtual memory
and is forcibly killing Jenkins and/or an individual build.
The following wiki page gives some hints at how to diagnose memory issues.
https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError
I've just added a bit about the error that I suspect you are seeing.
If you can't slim down the memory usage of Jenkins/your builds then you
will need to make more virtual memory available (either by adding
physical memory or some swap space). You may also be able to turn on
memory overcommit by setting /proc/sys/vm/overcommit_memory but that
does come with risks (sorry I don't have a link handy to describe what
that does).
Richard
If I can build the project via command line just fine when the Jenkins
server is running (meaning more than one JVM), isn't that a problem with
the Jenkins? I tried different combinations of fork configurations and
Maven JVM settings, even when build is OK for once, then it fails in
subsequent builds.
I even set maximum number of builds to keep to 3, but it didn't help.
Any comments are appreciated.
Best regards,
Deniz
