Configuring the WLS Diagnostic Framework Module Leads to a Memory Leak (Doc ID 2316724.1)

Last updated on JUNE 05, 2024

Applies to:

Symptoms

When diagnostic modules are configured, it may lead to a memory leak.

Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server

After configuring diagnostic modules and starting a server instance, heap size slowly grows. Mainly the following objects:

e.g.
com.oracle.weblogic.diagnostics.expressions.AttributeTerm
java.lang.ref.Finalizer
com.oracle.weblogic.diagnostics.expressions.ValueTracingELResolver$RawTrackedValue
weblogic.diagnostics.metrics.BeantreeInterceptor

You can check above objects from heapdump. This problem will lead to full GC and a high CPU usage percentage.

To get heapdump, use jmap or jrcmd. Refer "<Note 1922891.1> SRDC - Collect WebLogic Server Diagnostic Data - RDA, Thread and Heap Dumps" for details.

Changes

Created diagnostic modules, action and policy expressions following the documentation:

Fusion Middleware Configuring and Using the Diagnostics Framework for Oracle WebLogic Server

Cause

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