If you enable commercial features after the JVM is started, and then invoke the operation "newRecording" on the MBean jdk.management.jfr, the server will not return.

Steps to reproduce (using JConsole):
1. Start JConsole without commercial features enabled. This will be our server.

2. Start another JConsole, and connect it to the first other one. This will be our client JConsole.

3. From the client JConsole instance, enable commercial features in the server JConsole instance: Go to the "MBeans" tab, select the bean "com.sun.management", "DiagnosticCommand/Operations", invoke the operation "vmUnlockCommercialFeatures".

Commercial Features are now enabled in the server JConsole instance.

4. From the client JConsole instance, create a new Flight Recording in the server JConsole instance: Select the bean "jdk.management.jfr" and "FlightRecorder/Operations", invoke the operation "newRecording".

The server JConsole instance no longer responds.

Currently this stops JMC from starting new flight recordings in the JVM (if commercial features was not enabled when the JVM started). It will potentially destroy the JVM that is being monitored, which is why this is a severe issue.