-
Bug
-
Resolution: Fixed
-
P3
-
7
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2163743 | 6u10 | Luis-Miguel Alventosa | P3 | Resolved | Fixed | b31 |
There are two issues in the way the SnapshotMBeanServerConnection (introduced in JDK 6) is used within JConsole:
- JConsole Plugins:
The call to JConsoleContext.getMBeanServerConnection() should return the original
MBeanServerConnection but returns the SnapshotMBeanServerConnection.
- MBeans tab:
The Attributes are computed by calling getAttributes first and if an error occurs
then we call getAttribute for each individual attribute in the list.
The problem comes from the fact that the individual getAttribute calls go through
the SnapshotMBeanServerConnection that calls again getAttributes internally.
- JConsole Plugins:
The call to JConsoleContext.getMBeanServerConnection() should return the original
MBeanServerConnection but returns the SnapshotMBeanServerConnection.
- MBeans tab:
The Attributes are computed by calling getAttributes first and if an error occurs
then we call getAttribute for each individual attribute in the list.
The problem comes from the fact that the individual getAttribute calls go through
the SnapshotMBeanServerConnection that calls again getAttributes internally.
- backported by
-
JDK-2163743 REGRESSION: Bad usage of SnapshotMBeanServerConnection in MBeans tab and JConsole plugins.
- Resolved
- relates to
-
JDK-6714244 Plotters in MBeans tab should use SnapshotMBeanServerConnection too
- Closed
-
JDK-6699785 JMX monitoring doesn't show any values IF jconsole as per JDK6 AND standalone instance through NA
- Closed