The JFR Recording WLDF_Debug_Events Should Start with Bounds on Size
(Doc ID 2721979.1)
Last updated on OCTOBER 26, 2020
Applies to:Oracle WebLogic Server - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
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.
WLS debug flag "DebugDiagnosticDataGathering" was automatically enabled and provoked the recording named "WLDF_debug_events" to generating JFR files, causing performance issues.
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