Jetty process killed

Talking to DO support, it seems like the dropplets don’t have any swap partition set up by default. Setting up some swap space on our droplet appeared to solve this problem for us.

I believe that I’ve found the problem…just my droplet has 1GB of RAM, and jetty service was configured with 768mb form Xmx arg, the java process might have finished because cannot allocate all required memory. <br> <br>The service is running ± 10 hours without interruption.

Reliving this thread, <br> <br>I have the same situation. Sometimes the jetty process is simply stopped, and your log doesn’t have any memory leak. <br> <br>My droplet configuration is: 1GB RAM, 30GB disk…with Ubuntu 12.04 x64 <br> <br>My Jetty is 7.6, and this is your settings at /etc/default/jetty: <br> <br>JAVA_HOME=/usr/lib/jvm/jdk1.7.0_45 <br>JAVA=$JAVA_HOME/bin/java <br>JAVA_OPTIONS=" -server -Xms128m -Xmx512m -XX:+DisableExplicitGC -Dorg.eclipse.jetty.server.Request.maxFormKeys=900000 -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000" <br>JETTY_HOME=/usr/lib/jvm/jetty-distribution-7.6.13 <br>JETTY_USER=root <br>JETTY_PORT=8080 <br>JETTY_HOST=0.0.0.0 <br>JETTY_LOGS=$JETTY_HOME/logs/ <br> <br>Any idea about this situation ? :/ <br> <br>Thanks in advance.

I’m seeing similar problems - processes suddenly get killed with no apparent reason. This includes postgresql and rake spec (ruby on rails testing process)…

Sounds right. <br> <br>Also be mindful that even with constant utilization if a process doesn’t have absolutely perfect garbage collection its RAM utilization will creep up over time, which is often why there will be a master daemon that launches children so that they could be routinely cleaned out.

Apparently it was running out of memory. A quick fix java -Xmx64m