Details

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

      Operating System: All
      Platform: Macintosh

    • Issuezilla Id:
      275

      Description

      I often use visualvm to check out production servers that we use on different
      projects (usually there are several servers per project). VisualVM remembers all
      the remote servers that I ever configure it to connect and tries to connect to
      all of them when visualvm starts. This is unnecessary and only makes the startup
      slow.

      What I'm proposing, is to have a feature called remote server groups or
      profiles. User would be able to create a new group/profile and add remote
      servers to it.

      Then when visualvm starts, it will not try to connect to any of the remote
      servers, but instead will wait for the user to pick one or more of the
      groups/profiles that should be activated. Only at this time will visualvm try to
      connect to the servers.

      I believe that such a feature would make it easy for people to quickly connect
      to the desired servers, while prevent visualvm from wasting time by connecting
      to servers that a user is currently not interested in.

      bonus feature: export & import of server group config, so that it is easy to
      share them among visualvm installations or users.

        Activity

        Hide
        jsedlacek added a comment -

        Note that this can be achieved by switching the VisualVM userdir which can be
        treated as a kind of user profile. Example: visualvm --userdir servergroup1.

        In general, this can be easily implemented even without introducing the profiles
        just by adding a single 'monitoring on/off' switch for each server.

        Show
        jsedlacek added a comment - Note that this can be achieved by switching the VisualVM userdir which can be treated as a kind of user profile. Example: visualvm --userdir servergroup1. In general, this can be easily implemented even without introducing the profiles just by adding a single 'monitoring on/off' switch for each server.
        Hide
        iminar added a comment -

        That works, but it's really just a hack

        The disadvantages are:

        • I lose all the settings
        • I lose all the installed plugins
        Show
        iminar added a comment - That works, but it's really just a hack The disadvantages are: I lose all the settings I lose all the installed plugins

          People

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

            Dates

            • Created:
              Updated: