Wednesday June 28, 2006 Changes to the MBeans tab look and feel in Mustang JConsole
Moving the nested tabs for Attributes/Operations/Notifications/Info from the MBean's right panel to the MBean tree in the left panel has implied modifications to the MBeans tab look and feel.
Let's introduce the new Mustang JConsole features by comparison with the Tiger JConsole MBeans tab look and feel.
In Tiger JConsole when an MBean didn't have any attributes or operations or it wasn't a notification broadcaster the corresponding nested tab was greyed out.
The picture below depicts the Tiger JConsole MBeans tab for an MBean whose managament interface contains attributes and operations but no notifications.
In Mustang JConsole when expanding an MBean node in the MBean tree the Attributes/Operations/Notifications subnodes denote the nested tabs and they are present only if the MBean has attributes or operations or it is a notification broadcaster.
The picture below depicts the Mustang JConsole MBeans tab for an MBean whose managament interface contains attributes and operations but no notifications.
The information that could be found in the Info nested tab can be now found directly when selecting the MBean node. When the MBean node is selected the MBean's right panel displays its MBeanInfo. The notifications metadata was also displayed in the Info nested tab in Tiger JConsole when the MBean was a notification broadcaster and it is now displayed in the corresponding individual notification node as we will see later on.
The picture below depicts the Tiger JConsole Info nested tab.
The picture below depicts the Mustang JConsole MBean node.
In Mustang JConsole you can also see the MBean constructors metadata (MBeanConstructorInfo) in the MBean node with their associated parameters metadata (MBeanParameterInfo).
The picture below depicts the Mustang JConsole MBean node for an MBean com.example.mxbeans.QueueSampler which defines the constructor public QueueSampler(Queue queue).
The Attributes panel hasn't changed. It's the same as the Attributes nested tab in Tiger JConsole.
The picture below depicts the Tiger JConsole Attributes nested tab.
The picture below depicts the Mustang JConsole Attributes node.
What has changed is that now each individual attribute can be seen alone with its associated metadata.
The picture below depicts the Mustang JConsole Attribute node for the ThreadCount int attribute. In the right panel we can see the Attribute value, the MBeanAttributeInfo and its associated Descriptor information.
The Operations panel hasn't changed. It's the same as the Operations nested tab in Tiger JConsole.
The picture below depicts the Tiger JConsole Operations nested tab.
The picture below depicts the Mustang JConsole Operations node.
What has changed is that now each individual operation can be seen alone with its associated metadata.
The picture below depicts the Mustang JConsole Operation node for the CompositeData[] dumpAllThreads(boolean,boolean) operation. In the right panel we can invoke the operation, see the MBeanOperationInfo and its associated Descriptor information.
The Notifications panel hasn't changed. It's the same as the Notifications nested tab in Tiger JConsole.
The picture below depicts the Tiger JConsole Notifications nested tab.
The picture below depicts the Mustang JConsole Notifications node.
What has changed is that now each individual notification can be seen alone with its associated metadata.
The picture below depicts the Mustang JConsole notification node for the javax.management.Notification notification. In the right panel we can see the MBeanNotificationInfo and its associated Descriptor information.
In Tiger JConsole when selecting a notification broadcaster MBean for which we have subscribed for notifications we can see the number of received notifications inside brackets in the Notifications nested tab title.
The picture below depicts the Tiger JConsole Notifications nested tab for the AWTEvents MBean. In the title of the Notifications nested tab we can see that 19 notifications have been received for the given MBean.
In Mustang JConsole this functionality has been moved to the MBean tree too with the advantage that now we can see how the number of received notifications evolves in several MBeans at the same time. If a new notification arrives and the current notification broadcaster MBean is not the one selected in the MBean tree the number of notifications for the given MBean is displayed in boldface in the Notifications node label.
The picture below depicts the Mustang JConsole Notifications node for the AWTEvents MBean. In the Notifications node label we can also see that 19 notifications have been received for the given MBean but what's new here is that we can also see that 9 notifications have been received for the Notifier MBean and we haven't looked at some of them yet as denoted by the boldface label.