The JFR Recording WLDF_Debug_Events Should Start with Bounds on Size (Doc ID 2721979.1)

Last updated on JANUARY 13, 2023

Applies to:

Symptoms

There are issues with the filesystem occupation when, (with no apparent explanation) "WLDF_debug_events" recording is launched in one of the WebLogic instances.

WebLogic server is started with some JFR parameteres to activate default recording: -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:HeapDumpPath=/srv/log/core -XX:+HeapDumpOnOutOfMemoryError -XX:FlightRecorderOptions=defaultrecording=true,repository=xxx,maxage=1h,disk=true,dumponexit=true,dumponexitpath=xxx

Doc ID 2647815.1 which points to the WLS flag "DebugDiagnosticDataGathering", if it is activated the recording named "__WLDF_debug_events" starts generating JFR files.

Changes

 WLS debug flag "DebugDiagnosticDataGathering" was automatically enabled and provoked the recording named "WLDF_debug_events" to generating JFR files, causing performance issues.

Cause

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