My Oracle Support Banner

Observing "OutOfMemoryError" and Frequent Full Garbage Collections in WebLogic After Pointing Datasources to a 19c Database (Doc ID 2751978.1)

Last updated on AUGUST 03, 2023

Applies to:

Oracle WebLogic Server - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

When pointing the WebLogic Datasources to point to a 19c Database, there are a lot of "OutOfMemoryError" and frequent full Garbage Collections (GCs). The same WebLogic instance works fine with a 11g Database.

The analysis of heap dumps show nearly 30k instances of "oracle.jdbc.driver.T4CConnection", loaded by "com.oracle.classloader.weblogic.LaunchClassLoader and these instances are referenced from one instance of "java.util.concurrent.ConcurrentHashMap$Node[]".  The memory leak is on oracle.jdbc.driver.HAManager.

The path to GC for oracle.jdbc.driver.T4CConnection looks like this:

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
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.