Re: Instable builds related to low memory

2012-03-09 Thread Deniz Acay
On 03/09/2012 08:20 PM, Sami Tikka wrote: Exit code 137 = 128 + 9 => The process died because it received a signal and the signal was 9 which is SIGKILL. SIGKILL is the signal Linux out-of-memory killer uses to get rid of memory hogs. It sure sounds like you might not have enough memory. But I

Re: Instable builds related to low memory

2012-03-09 Thread Sami Tikka
Exit code 137 = 128 + 9 => The process died because it received a signal and the signal was 9 which is SIGKILL. SIGKILL is the signal Linux out-of-memory killer uses to get rid of memory hogs. It sure sounds like you might not have enough memory. But I cannot answer why it takes more memory when J

Re: Instable builds related to low memory

2012-03-09 Thread Richard Mortimer
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 Jenk

Re: Instable builds related to low memory

2012-03-09 Thread Didier Durand
Hi, Did you try to try Java heap size via the "Java options" (advanced section) of the step config parameters using Xnx and Xms ? That should solve your issue. [I dodn't think the size of physical real memory really matters for completion: even if you allocate more heap than physical memory, y

Instable builds related to low memory

2012-03-09 Thread Deniz Acay
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.