Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-7118025

JConsole default values of true, 0 and String are dangerous - MBeans tab

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: P4 P4
    • tbd
    • 7
    • tools
    • x86
    • windows_xp

      A DESCRIPTION OF THE REQUEST :
      For JMX Operations on the MBeans tab in JConsole, default values are populated in method parameters as:
         * true - boolean
         * 0 - numeric (e.g. int)
         * "String" - string

      JUSTIFICATION :
      It seems too easy for administrative users to click on an MBean operation button. For a lot of operations, 0 and true will be dangerous values. For example, if you're setting a threshold of something, 0 is often a nonsensical value.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      The value TextField inputs should start in a "dirty" state, highlighted in a light red background color and should have values of:
         * boolean
         * int
         * String

      The MBean operation button should be deactivated in this "dirty" state. It should only be activated when the user types valid parameter values.

      When clicking on one of these dirty values, the whole string should be selected so that when the user starts typing it replaces the value. These values stop being default values and instead should be regarded as descriptions.
      ACTUAL -
      You are currently able to submit the MBean operations using the default values of true and 0.

            Unassigned Unassigned
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Imported:
              Indexed: