All geek questions in one place

Parameters of Jboss eap 5.1 GC JMV

I am using Jboss eap 5.1 with Seam Framework. I want to configure my GC to avoid FullGC. I already use CMS GC. This will be my next configuration on a production system:

-Xms24g -Xmx24g -XX:+UseCompressedOops -XX:NewRatio=4 -XX:SurvivorRatio=8 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+DisableExplicitGC -XX:+UseCMSInitiatingOccupancyOnly -XX:+CMSClassUnloadingEnabled -XX:+CMSScavengeBeforeRemark -XX:CMSInitiatingOccupancyFraction=68

My question is: "Do I need to remove these JVM options" ?:

 -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

if i add this:

 -XX:+DisableExplicitGC

or should they stay together?

+4
source share
1 answer

You can enable both sets of options. But -XX:+DisableExplicitGC prevent any SystemGC calls coming from RMI sessions.

The recommended use is to either disable SystemGC alltogether using -XX:+DisableExplicitGC , or at least use the sun.rmi.dgc.*.gcInterval to control the frequency of System GC calls (so that the SystemGC system does not appear too often).

I would suggest using -XX:+DisableExplicitGC and see if the number of "dead" RMI objects is growing, if so, then you need to start the configuration using the sun.rmi.dgc.*.gcInterval .

It’s all stipulated that you really want to avoid Full GC, perhaps take a short pause. Full GC will not be such a bad idea, as you will need to clean up RMI objects.

+1
source

Source: https://habr.com/ru/post/1497371/

More articles:


All Articles