VMware GemFire: garbage collection (GC) logging arguments changed in Java 11

Products

• VMware Tanzu Gemfire

Issue/Introduction

When moving to Java 11, garbage collection (GC) arguments used in previous Java versions will need to be reviewed and may need to be replaced with new arguments and values to achieve the desired behavior.

The primary purpose of this article is to make you aware that such changes are needed and encourage proactive research with your team and GC experts to make sure that you are using the appropriate settings when using Java 11 or later.

Environment

Product Version: 9.10
OS: JAVA 11

Resolution

Rather than reinvent the wheel, we recommend reviewing the following resource: https://stackoverflow.com/questions/54144713/is-there-a-replacement-for-the-garbage-collection-jvm-args-in-java-11

In addition, Oracle describes these in even more detail in the following documentation: https://docs.oracle.com/javase/9/tools/java.htm#JSWOR624

VMware GemFire is an application running in a JVM. You must have some expertise in the configuration and behavior of GC in your environment, including the finer tuning of your application given the heap and CPU provisioned.  

VMware GemFire Support can be engaged to assist, but in-house expertise is needed and the finer tuning of GC will generally fall to our field consulting engineering teams.