Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1577

After a full-replace-deployment operation a server on a hosts subsystem model is empty

    XMLWordPrintable

Details

    Description

      Executing a full-replace-deployment operation on a deployment deployed to a server in a managed domain will result a servers subsystem model to be an empty list.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1687 WFLYCTL0357 warning upon undeploying any deployment

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6897 Replacing a disabled deployment destroys profile section of xml config

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-495 WFLY won't startup due to "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"xxx.war\")]"

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-6598 [GSS](7.1.0) Replacing a disabled deployment destroys profile section of xml config

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              bstansbe@redhat.com Brian Stansberry
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: