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

[GSS](7.1.0) Replacing a disabled deployment destroys profile section of xml config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR7
    • 7.0.2.GA
    • Management, Server
    • None

      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

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

                Created:
                Updated:
                Resolved: