[Bug 541520] [NEW] Using incorrect JVM Garbage Collector

[Aaron J. Zirbes]

Public bug reported:

Binary package hint: tomcat6

The default garbage collector for tomcat should be the Concurrent Mark-
Sweep (CMS) Collector as it is the recommended GC for Web Application
Severs.

The default garbage collector doesn't guarantee quick response times,
and often times causes hangs during garbage collection.

As Tomcat 6 is a web application server, it should use the CMS GC.

Here is the diff to fix it:

diff /etc/default/tomcat6 /etc/default/tomcat6.original
17a18,20
> # Use a concurrent garbage collector for improved response time
> JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC"
> 


To do this, the following option can be added to `/etc/default/tomcat6`

...

# Arguments to pass to the Java virtual machine (JVM).
#JAVA_OPTS="-Djava.awt.headless=true -Xmx128M"

# Use a concurrent garbage collector for improved response time
JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC"

...


Reference:
http://java.sun.com/javase/technologies/hotspot/gc/memorymanagement_whitepaper.pdf

Additional Material:
http://java.sun.com/javase/technologies/hotspot/gc/index.jsp

Thanks for making Ubuntu Server enterprise ready!

** Affects: tomcat6 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Using incorrect JVM Garbage Collector
https://bugs.launchpad.net/bugs/541520
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.