-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
2.1, 6
-
generic
-
generic
Today the MBean tab in JConsole has a refresh button that refreshes the values of the
displayed attributes of the selected MBean. However, this button does not refresh
the MBean tree. Refresh of the MBean tree is triggered by MBean creation/deletion
notifications.
It would be good to have also a button that forces JConsole to refresh the MBean tree.
Some products, such as Java DMK, make it possible to implement virtual MBeans
on top of JMX 1.2. For such MBeans, creation/deletion notifications are not
necessarily emitted.
Having a manual refresh mechanism would greatly improve the usability of
JConsole when connected to such implementations.
note also that a notification storm and a possible jmx.remote.connection.notifs.lost notification means that jconsole will not necessarily be up to date with
respect to mbean instances, so having a 'refresh' button is very useful even
within the JMX spec without talking about JDMK interceptors and JMX 2.0's planned work around virtual mbeans.
displayed attributes of the selected MBean. However, this button does not refresh
the MBean tree. Refresh of the MBean tree is triggered by MBean creation/deletion
notifications.
It would be good to have also a button that forces JConsole to refresh the MBean tree.
Some products, such as Java DMK, make it possible to implement virtual MBeans
on top of JMX 1.2. For such MBeans, creation/deletion notifications are not
necessarily emitted.
Having a manual refresh mechanism would greatly improve the usability of
JConsole when connected to such implementations.
note also that a notification storm and a possible jmx.remote.connection.notifs.lost notification means that jconsole will not necessarily be up to date with
respect to mbean instances, so having a 'refresh' button is very useful even
within the JMX spec without talking about JDMK interceptors and JMX 2.0's planned work around virtual mbeans.