When establishing a connection to a runtime that does not included required jdk.management modules, JMC will silently connect to its own runtime.

The impacted features are :

• Starting JMX console :
• Starting a flight recording session
• Dump Heap
• JMC agent

There should be a better and descriptive fallback when the target runtime does not contain management related modules.