My Oracle Support Banner

Managed Instance(s) Crashing Due To Failed Concurrent Java Garbage Collection (Doc ID 2264427.1)

Last updated on DECEMBER 12, 2018

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.4.0.2.0 and later
Information in this document applies to any platform.

Symptoms

Managed instance(s) crashing due to failed concurrent java garbage collection

Problem Description
---------------------------------------------------
A few times per month, individual managed instances of weblogic suddenly appear to stop serving requests, leaving messages related to garbage collection in the stdout log files for that instance, and with Full GC failure messages in our gcverbose log files. When this situation occurs, that instance stops handling requests entirely (other managed instances continue performing fine).


Example of failure messages in gcverbose log:




the issue occurs when a sudden increase in used-memory would reach any maximum amount configured in a very short amount of time. Even the setting that requests a collection at 70% wasn't really soon/fast enough to stop this sudden increase.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.