JDK 17 introduced a more advanced parser for reading .jfc files. This to allow .jfc options to be configured using -XX:StartFlightRecording and JFR.start.

Problem is that default.jfc and profile.jfc are loaded without FilePermission, which could lead to a SecurityException if JFR is used with a security manager. This is not the case for the older parser, which is planned to be decommissioned once default.jfc and profile.jfc configuration can be loaded using jlink mechanism.

Workaround is for the user to configure permission themselves so the JVM can read JAVA_HOME/lib/jfr/default.jfc and JAVA_HOME/lib/jfr/profile.jfc.