1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Tuning Garbage Collection in Apache Tomcat

Discussion in 'Main Forum' started by arashsami, Sep 12, 2018.

  1. arashsami

    arashsami Guest

    I have the following parameters in tomcat6.conf

    JAVA_OPTS="-server -Xmx6144m -Xms3072m -XX:+UseConcMarkSweepGC -XX:MaxGCPauseMillis=999 -XX:ReservedCodeCacheSize=128m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname= -Djava.rmi.server.useLocalHostname=false"

    but at peak time I see the following regularly,

    ERROR memory-watcher - used 87.73865761212004%, max 6403194880 reaping at priority CRITICAL

    is there any parameter I can use to to tune tomcat performance or GC ?

    Login To add answer/comment

Share This Page