What to do when Java Garbage Collection is Monitored, and the Memory is not Cleared as Expected?
Last updated on OCTOBER 16, 2016
Applies to:Oracle Health Insurance Claims Adjudication - Version 2.14.2 and later
Information in this document applies to any platform.
Java Garbage Collection (gc), is a process to clear memory.
What steps need to be taken when monitoring Java Garbage Collection, i.e., using jstat, and it shows that memory is not cleared as expected?
What steps should be taken when Java Garbage Collection is showing a high memory consumption, for instance above 80 to 90%?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms