Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6599

[GSS](7.0.z) Replacing a disabled deployment destroys profile section of xml config

    XMLWordPrintable

Details

    • EAP 7.0.4

    Description

      This issue is related to an already closed JIRA for wildfly 10.0.0.Final (https://issues.jboss.org/browse/WFLY-6897)

      When replacing a deployment that is disabled at the time of replacement, Wildfly will write out a new configuration .xml that is missing the entire <profile> section, resulting in an application server that is, essentially, non-functional once restarted. There is no obvious effect until restart.

      Pull request for fixing this issue for wildfly: https://github.com/wildfly/wildfly-core/pull/1598/files?diff=unified

      Attachments

        Issue Links

          clones

          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
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-6603 (7.0.z) Upgrade WildFly Core from 2.1.9.Final-redhat-1 to 2.1.10.Final

          • 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
          relates to

          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

          Activity

            People

              chaowan@redhat.com Chao Wang
              rhn-support-mcarvalh Marcus Carvalho (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: