[jboss-jira] [JBoss JIRA] (WFLY-6897) Replacing a disabled deployment destroys profile section of xml config

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved WFLY-6897.
------------------------------------
    Fix Version/s: 10.1.0.CR1
         Assignee: Brian Stansberry  (was: Jason Greene)
       Resolution: Done


The WFCORE-1577 fix is in WildFly 10.1.0.CR1.

> Replacing a disabled deployment destroys profile section of xml config
> ----------------------------------------------------------------------
>
>                 Key: WFLY-6897
>                 URL: https://issues.jboss.org/browse/WFLY-6897
>             Project: WildFly
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 10.0.0.Final
>         Environment: Fresh install of Wildfly 10 on Ubuntu 15.10 / JDK 8_101
>            Reporter: Brian Rozmierski
>            Assignee: Brian Stansberry
>             Fix For: 10.1.0.CR1
>
>
> 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.
> Also note there is a forum post reporting this behavior from April.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)