FULL PRODUCT VERSION :
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
In Java 5 it was easy to access an selected MBeans' attributes, operations, and notifications via tabs in the MBean details panel (i.e. the panel on the right side of the main splitter in the MBean tab and thus to the right of the MBean tree).
In Java 6 there are several serious usability issues:
1) One must go back to the MBean tree to access these aspects of a selected MBean. This is not a huge deal, but is a step back in usability, especially for those used to Java 5's jconsole.
2) The Attributes, Operations, and Notifications nodes in the MBean tree are not sorted in any way with respect to other child nodes of a given MBean tree node. Nor are the nodes differentiated from other non-MBean child nodes in any way. Thus when an MBean tree node has many child nodes it quickly becomes quite onerous to find the MBean's attributes, operations, and notifications!
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Point Java 6 jconsole at any MBeans that had existing child nodes in the MBean tree in Java 5.
EXPECTED VERSUS ACTUAL BEHAVIOR :
I can understand behavior (1) from the description above, though I'd expect the details tab to provide some sort of quick/obvious access to the attributes, operations, and notifications. Putting the tabs back and having them behave as if one selected the corresponding tree node would be helpful. Still I can kind of see this being delayed until Java 7.
What I cannot understand is behavior (2). The Attributes, Operations, and Notifications nodes should always be sorted to the top of an MBean's list of child nodes and should be given a different icon so as to differentiate them from other child nodes. This should be considered a *bug* for immediate redress and is in no way an enhancement. As it stands now this is a serious usability regression from Java 5.
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Use Java 5 jconsole instead -- and loose all the nice new functionality from Java 6's jconsole.