VisualVM
  1. VisualVM
  2. VISUALVM-281

MBean plugin: The information in ModelMBeanOperationInfo's Descriptor is ignored

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1.1
    • Fix Version/s: not determined
    • Component/s: plugins
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      281

      Description

      Hi,
      as per the jmx spec, ModelMBeanOperationInfo class has a Descriptor which has
      the following property:

      • role: must be "operation", "getter", or "setter

      VisualVM is ignoring this property however. This results in a situation, where
      an attribute's methods are exposed twice. For example, if you have a
      setName/getName for the name attribute, VisualVM shows the "name" attribute in
      Attributes section.

      But then, it also shows those as operations in the "Operations" section.

      This creates so many operations (2 per attribute + the rest of the actual
      operations).

      Can we get this fixed please?

        Activity

        Hide
        jsedlacek added a comment -

        Could you please check how this works in JConsole? VisualVM is just reusing it's
        MBeans browser, this doesn't seem like a VisualVM problem to me...

        If I understand it correctly no operation/information is missing, some features
        are just duplicated -> lowering priority, harmless.

        Show
        jsedlacek added a comment - Could you please check how this works in JConsole? VisualVM is just reusing it's MBeans browser, this doesn't seem like a VisualVM problem to me... If I understand it correctly no operation/information is missing, some features are just duplicated -> lowering priority, harmless.
        Hide
        celalziftci added a comment -

        It works the same way in JConsole too.

        As you mention, the problem is about duplication. But I would consider this to
        be a big problem in usability, because way too many operations appear because of
        this.

        Show
        celalziftci added a comment - It works the same way in JConsole too. As you mention, the problem is about duplication. But I would consider this to be a big problem in usability, because way too many operations appear because of this.
        Hide
        celalziftci added a comment -

        Hi,
        is there any update on this? We are keen on understanding why things work this
        way in JConsole/VisualVM.

        Show
        celalziftci added a comment - Hi, is there any update on this? We are keen on understanding why things work this way in JConsole/VisualVM.
        Hide
        jsedlacek added a comment -

        Speaking for VisualVM, things work this way just because it uses the MBeans
        browser from JConsole. Probably a question for JConsole?

        Show
        jsedlacek added a comment - Speaking for VisualVM, things work this way just because it uses the MBeans browser from JConsole. Probably a question for JConsole?
        Hide
        celalziftci added a comment -

        OK, we will report this to JConsole then.

        Show
        celalziftci added a comment - OK, we will report this to JConsole then.

          People

          • Assignee:
            visualvm-issues
            Reporter:
            celalziftci
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: