On 24/02/18 18:52, Industrious wrote: > Dear All, > > I am running Tomcat 8 on Ubuntu. After a few days of running > successfully my Tomcat's JVM crashes or becomes absolutely unresponsive > because of OOME errors similar to this in catalina.out:
<snip/> > At first I was using GCE micro instance with 600MB of RAM. Soon I > started having problems when Linux was killing Tomcat (OOM killer) as it > considered its JVM as a candidate for killing or if I specify a lower > maximum heap size I would eventually get OOME from JVM. > > I moved to a GCE small instance which has 1.7GB of RAM but the problem > still occurs eventually though a bit later than on the 600MB VM because > I somewhat increased the maximum heap size. <snip/> > $ less /var/lib/tomcat8/bin/setenv.sh > JAVA_OPTS="-Dlog4j.logging.dir=$CATALINA_BASE/logs \ > -Dlogging.dir=$CATALINA_BASE/logs \ > -Djava.awt.headless=true \ > -Xms220M \ > -Xmx220M \ > -Dsun.java2d.cmm=sun.java2d.cmm.kcms.KcmsServiceProvider \ > -Djava.security.egd=file:/dev/./urandom \ > -XX:+HeapDumpOnOutOfMemoryError \ > -XX:HeapDumpPath=$CATALINA_BASE/logs/java_pid%p.hprof" Looks like you need to increase Xmx and use some of that extra memory you paid for. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
