JConsole MBean tab displays MBean based on ObjectName.
The algorithm to attach node in the tree is based on ObjectName key original order.
If Ojectname have similar keys but not ordered the same way, MBeans will be not aggregated under the same node.
An homogeneous and configurable behavior should be implemented.
From ###@###.###:
[Concerning the best-practices document at <http://java.sun.com/products/JavaManagement/best-practices.html>]
One aspect of the best practices guide troubles me: the definition of names for contained objects.

 

Originally, I defined my names in the following way:

OSProcess=Process for SOAP processor monitor@cnd0966

OSProcess=Process for SOAP processor monitor@cnd0966,ldapCache=LDAP cache

OSProcess=Process for SOAP processor monitor@cnd0966,processor=monitor@cnd0966

OSProcess=Process for SOAP processor monitor@cnd0966,processor=monitor@cnd0966,soapConnector=SOAP Connector

The JConsole nicely renders a tree structure out of these names.

 

To comply to the best practice pattern, I’ve changed the names this way:

name="Process for SOAP processor monitor@cnd0966",type=OSProcess

name="LDAP cache",type=OSProcess.ldapCache,OSProcess="Process for SOAP processor monitor@cnd0966"

name="monitor@cnd0966",type=OSProcess.processor,OSProcess="Process for SOAP processor monitor@cnd0966"

name="SOAP Connector",processor="monitor@cnd0966",type=OSProcess.processor.soapConnector,OSProcess="Process for SOAP processor monitor@cnd0966"

Now JConsole gets completely confused about the containment hierarchy.

Am I doing something wrong or is it JConsole?

If it is, will there be a new version of JConsole that implements the naming pattern?