glassfish
  1. glassfish
  2. GLASSFISH-10340

delete-system-property should include the element name as well while printing the error

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: V3
    • Fix Version/s: future release
    • Component/s: admin
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: PC

      Description

      When you try to delete the system property which is in use it fails with the
      message that the property is in use. But it doesn't print the config element in
      which the property is referenced.

      In the following case the listener httpls1 is referencing the property, the
      error message should say the property is in use by the element httpls1.

      aroot@easqeopt19:~# asadmin delete-system-property port
      com.sun.enterprise.admin.cli.CommandException: remote failure: System Property
      port is referenced by [network-listener:port] in the configuration. Please
      remove the references first.

      Command delete-system-property failed.

      aroot@easqeopt19:~# asadmin get "*" | grep httpls1
      configs.config.server-config.network-config.network-listeners.network-listener.httpls1.port=$

      {port}

        Activity

        Hide
        km added a comment -

        Sure, later.

        Show
        km added a comment - Sure, later.
        Hide
        Tom Mueller added a comment -

        Upping the priority based on the age of the issue. Changing this to an RFE.

        This is a change to the DeleteSystemProperty.listRefs method, to add the value of a "name" attribute, if it exists.

        Show
        Tom Mueller added a comment - Upping the priority based on the age of the issue. Changing this to an RFE. This is a change to the DeleteSystemProperty.listRefs method, to add the value of a "name" attribute, if it exists.
        Hide
        Tom Mueller added a comment -

        A fix for this issue was initially identified for possible inclusion in the 3.2 release, but after further 3.2 planning, the feature or improvement did not make the cut. This issue is being targeted for a future release. If based on a reevaluation, it is targeted for 3.2, then update the "fix version" again.

        Show
        Tom Mueller added a comment - A fix for this issue was initially identified for possible inclusion in the 3.2 release, but after further 3.2 planning, the feature or improvement did not make the cut. This issue is being targeted for a future release. If based on a reevaluation, it is targeted for 3.2, then update the "fix version" again.

          People

          • Assignee:
            kumara
            Reporter:
            sankarpn
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: