JDK-6439590 : MBeans tab: jconsole mbean tree not correctly refreshed
  • Type: Bug
  • Component: tools
  • Sub-Component: jconsole
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-06-16
  • Updated: 2011-04-19
  • Resolved: 2011-04-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u10Fixed 7 b25Fixed
Related Reports
Duplicate :  
JDK-6748331 - Deadlock in JConsole due to AWT operations performed outside EDT
Relates :  
JDK-6446434 - MBeans tab: Not possible to view MBean content before all MBeans have been initially loaded
Description
With JConsole provided by Tiger update 6 and Mustang b87,
1 - Connect Jconsole to a cacao agent
2 - Choose MBean tab
3 - Expand a domain
4 - Register 2000 mbeans in this domain

The MBean tree freeze and user can't select all MBeans.

Note that if you ask for a new connection, the MBean tree is correct.
Comments
EVALUATION Delay this bug fix till Dolphin as it concerns very sensitive code. In Dolphin all the MBean tree construction logic should be rewritten using the SwingWorker class.
22-06-2006
WORK AROUND There exists a workaround in Mustang JConsole. Just let the JMX agent create/delete all the MBeans and wait for JConsole to handle all the register/unregister MBean notifications. Then disconnect and connect again using the new disconnect/reconnect button. This will provoke a refresh of the MBean tree with the correct MBean server view.
22-06-2006
EVALUATION Looks like a synchronization problem when building the MBean tree.
16-06-2006