[Bug] JFR operations require MissionControlMXBean

[andrewazores]

I think that probably explains the difference in behaviour for different operations, though. The Dashboard MBean Metrics views are powered by opening a JMX connection and directly invoking remote calls on various M(X)Beans, like the OperatingSystemMXBean or MemoryMXBean. JFR operations like starting a recording or listing .jfc event templates open a JMX connection and then go through a JMC library call stack, which I'm sure hits that HotspotManagementToolkit and therefore requires the MissionControl MXBean.

Originally posted by @andrewazores in cryostatio/cryostat#595 (reply in thread)

[andrewazores]

TODO: investigate feasibility of removing the linked toolkit class from the call path. It doesn't seem like we really need the MissionControlMXBean for Cryostat's purposes.

Removing the JMC dependencies from the JFR management operation call paths would also do the job, but would be a very large refactoring job related to #223, #173.

Either directly reimplementing the operations, or using a simpler library like https://github.com/microsoft/jfr-streaming , could help.