When turning a given JVM object into a JMX server connection, the underlying impl only exposes the name of the main class that was used to start the process. This is not enough information to correctly differentiate various server types from each other.

This is a pre-requisite to accurately detecting duplicates in the JMX view and ensuring they don't pollute the view. It's also important to correctly match detected jvms with top-level jmx connection nodes such as the Wildfly nodes or EAP nodes.