glassfish
  1. glassfish
  2. GLASSFISH-5023

inconsistent behaviour of system-properties config

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 9.1peur2
    • Fix Version/s: 4.0_b80_EE7MS6, 4.0
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5,023

      Description

      The usage of system properties is unclear and not consistent using asadmin vs.
      admin GUI.

      Example:
      1.) asadmin create-system-properties --target testcluster-config name1=value1
      => OK: Value is created and visible under
      Admin-GUI->configurations->testcluster-config->system-properties also asadmin
      list-system-properties shows name1=value1 for the instances
      => Not OK: If I go to admin gui->clusters->testcluster-><instance> and then
      select Properties Tab I don't see anything to override
      Expected: on the instance view (cluster->testcluster->instance->property) i
      would like to see cluster wide properties to be overwritable. If I go to
      configurations->...>system-properties>instance view everything is fine

      2.) asadmin create-system-properties --target testcluster name1=value1
      => system properties created on the --target <cluster> instead of
      <cluster-config> don't show up at all.
      => Difference between props for <cluster> vs. <cluster-config> unclear

      3.) if a create a cluster instance specific property using asadmin
      create-system-properties --target <cluster-instance-name> name3=value3 the admin
      gui gives errors
      =>OK: asadmin list-system-properties shows all
      => NOT OK: admingui > cluster>cluster-name->instance-name->properties shows an
      error about "An error has occurred Property name3 is not found in the element. "

        Activity

        Hide
        km added a comment -

        Again, I think there are multiple issues here. Are you worried about GUI
        representation of this? Please clarify and if you want better GUI
        representation, assign the bug to Admin_GUI category.

        Show
        km added a comment - Again, I think there are multiple issues here. Are you worried about GUI representation of this? Please clarify and if you want better GUI representation, assign the bug to Admin_GUI category.
        Hide
        barz26 added a comment -

        re-assigned to admin_gui as of km's notes

        Show
        barz26 added a comment - re-assigned to admin_gui as of km's notes
        Hide
        schaarsc added a comment -

        add \me to CC

        Show
        schaarsc added a comment - add \me to CC
        Hide
        sanandal added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        sanandal added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        Tom Mueller added a comment -

        Kedar no longer on project.

        Show
        Tom Mueller added a comment - Kedar no longer on project.
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.
        Hide
        Anissa Lam added a comment -

        We have redesigned the properties screen in v3. v4 screen is the same as in v3. The redesign was based on inputs from dev, doc and QA team.
        Marking as resolved.

        Show
        Anissa Lam added a comment - We have redesigned the properties screen in v3. v4 screen is the same as in v3. The redesign was based on inputs from dev, doc and QA team. Marking as resolved.

          People

          • Assignee:
            Anissa Lam
            Reporter:
            barz26
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: