¿Por qué obtengo GC completo en Java?

Why do I get full GC in Java?

Beside tuning the various options of JVM I would also suggest to upgrade to a newer release of the VM, because later versions have much better tuned garbage collector (also without trying the new experimental one).

Upon successful completion of a concurrent marking cycle, the G1 GC switches from performing young garbage collections to performing mixed garbage collections. In a mixed garbage collection, the G1 GC optionally adds some old regions to the set of eden and survivor regions that will be collected.

After a couple of days of uptime the Full GC starts occurring more frequently and it becomes a serious problem to the application’s availability. After a tomcat restart the problem goes away but, of course, returns after 5 to 10 or 30 days (not consistent). The Full GC log before and after a restart is at…

To start with, GC defines some specific objects as Garbage Collection Roots. e.g. local variable and input parameters of the currently executing methods, active threads, static field of the loaded classes and JNI references.

[PSOldGen: 684832K->699071K (699072K)] – After the GC ran the old generation space increased from 684832k (i.e. 669mb) to 699071k (i.e. 682mb) and total allocated old generation space is 669072k (i.e. 682mb). In this case after the GC event, old generation’s space increased and didn’t decrease, which isn’t the case always.

Beside that also if it’s (partially) true that assigning more ram to JVM could increase the time required to perform GC there is a tradeoff point between using the whole 16 GB of memory and increasing your memory occupation, so you can try double all values, to start

In order to understand the GC log, you first need to generate one. Passing the following system properties to your JVM would generate GC logs. -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc: . where file-path: Garbage Collection log file path.