Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3078

directory-grouping configuration is not getting persisted via CLI when no servers defined

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.1.0.CR1, 8.1.0.Final
    • 8.0.0.Final
    • Management
    • None
    • Hide
      • 1). Take a default "wildfly-8.0.0.Final" installation and Start in domain mode.
      • 2). Remove the default servers.
        /host=master/server-config=server-one/:stop
        /host=master/server-config=server-one/:remove
        /host=master/server-config=server-two/:stop
        /host=master/server-config=server-two/:remove
        /host=master/server-config=server-three/:stop
        /host=master/server-config=server-three/:remove
        
      • 3). Check the "host.xml" file the empty <servers></servers> tag is present.
      • 4) Apply the directory-grouping configuration.
        /host=master/:write-attribute(name=directory-grouping,value=by-type)
        
      • 5). Check the "host.xml", It can be seen that the <servers></servers> tag is removed. As the "directory-grouping" information is not persisted in the XML file hence it is lost when we restart the Host controller. So after restart we see the following
        [domain@localhost:9990 /] /host=master/:read-attribute(name=directory-grouping)
        {
            "outcome" => "success",
            "result" => "by-server"
        }
        

      Expected result: In "host.xml" file the "directory-grouping" should have persisted (by-type) so that it could survive the host restart.

      Show
      1). Take a default "wildfly-8.0.0.Final" installation and Start in domain mode. 2). Remove the default servers. /host=master/server-config=server-one/:stop /host=master/server-config=server-one/:remove /host=master/server-config=server-two/:stop /host=master/server-config=server-two/:remove /host=master/server-config=server-three/:stop /host=master/server-config=server-three/:remove 3). Check the "host.xml" file the empty <servers></servers> tag is present. 4) Apply the directory-grouping configuration. /host=master/:write-attribute(name=directory-grouping,value=by-type) 5). Check the "host.xml", It can be seen that the <servers></servers> tag is removed. As the "directory-grouping" information is not persisted in the XML file hence it is lost when we restart the Host controller. So after restart we see the following [domain@localhost:9990 /] /host=master/:read-attribute(name=directory-grouping) { "outcome" => "success" , "result" => "by-server" } Expected result: In "host.xml" file the "directory-grouping" should have persisted (by-type) so that it could survive the host restart.

    Description

      • If none of the servers are defined in "host.xml" (means <servers></servers> empty tag is present) and if the user tries to run the following CLI command to change the "directory-grouping" to "by-type" then the value is not persisted in the configuration file (host.xml) and the <servers></servers> tag is also removed from the host.xml
        /host=master/:write-attribute(name=directory-grouping,value=by-type)
        
      • The value of "directory-grouping" is stored "in memory" so this change does not survive the host restart.

      Attachments

        Activity

          People

            emuckenhuber_jira Emanuel Muckenhuber (Inactive)
            jaysensharma Jay SenSharma (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: