JDK-6174397 : Revisit jconsole UI design to make it more user-friendly
  • Type: Enhancement
  • Component: tools
  • Sub-Component: jconsole
  • Affected Version: 5.0u1
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-10-05
  • Updated: 2012-10-09
  • Resolved: 2006-03-06
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
6 rcFixed
Related Reports
Relates :  
JDK-6245902 - New Connection Dialog
Relates :  
JDK-6253724 - A new overview tab showing usage graphs of multiple critical resources in a single tab
Relates :  
JDK-6253467 - Provide a user-friendly way to enable/disable verbose:gc tracing
Relates :  
JDK-6247572 - Use system look-and-feel instead of Java look-and-feel
Description
jconsole is a JDK demo GUI in JDK1.5.
Need to revisit the UI design for a better user interface.
###@###.### 10/5/04 17:48 GMT

The java.lang.management API has other information available but only accessible through the MBeans tab.  There is no MBean specific tab to monitor or control some attributes.  For example,
  1. set -verbose:gc and -verbose:class on/off
  2. perform deadlock detection
  3. change log level (see 5052763)
  4. turn on/off thread monitor contention monitoring

We should consider to support these in our redesign.  The above can all be done in the MBeans tab.

###@###.### 10/14/04 19:16 GMT
###@###.### 10/14/04 19:16 GMT
Comments
EVALUATION This CR is an umbrella RFE for Mustang planning purpose. We added a new connection dialog, the new overview tab, deadlock detection UI in Mustang and also switched to use system LAF. It would be a contining effort to improve the usability of jconsole in the future release.
06-03-2006
EVALUATION Consider for Mustang. ###@###.### 10/5/04 17:48 GMT A heuristic evaluation was conducted on Feb 2-3, 2005 to identify and priorize the JConsole's UI issues. About 130 UI issues were identified. The following tasks were performed in the heuristic evaluation: 1. Connecting to a running JVM 2. Find out the process CPU time 3. Set up an alarm for monitoring memory usage against a specific threshold 4. Invoke an operation of a specific MBean 5. Set the log level of a specific logger 6. Get the thread dump of a specific thread 7. Check if any threads are in deadlock, and, if so, why New RFEs will be submitted to address UI issues in Mustang to make jconsole more user-friendly. This CR is an umbrella for the Mustang jconsole feature. ###@###.### 2005-04-11 19:23:38 GMT
05-10-2004