Wildfly 10 Final - Replace Disabled Deployment Problem

[wyll.cavalcante]

Hi everyone! I don't know if its a default behavior, but looks like a bug. If i replace a disabled war deployment, all my subsystem got deleted! My luck is that wildfly itself has that saving standalone.xml history mechanism.

We are already using Wildfly 10 final in a small production environment in my job, my friend told me that the management console was acting weird, testing in my aws server as well, i replaced a disabled deployment and then... Bum! All subsystems deleted!

Questioning myself about my job's problem, when i take a look ate the management console... Bum! All subsystems deleted too! So i think it's a real problem... Or maybe a behavior that i don't understand.

Some detais...

Job's enviroment

Cent Os 7

JDK 8_71

Wildfly 10.0.0 Final Standalone mode

My AWS Server environment

Ubuntu 14 LTS

JDK 8_11

Wildfly 10.0.0 Final Standalone mode

Thanks in advance.

[bdaroz]

I just wanted to chime in and say I can reproduce this on a nearly-stock Wildfly 10 instance, this time on Ubuntu 15.10 and JDK 8_101.

It's driving me nuts when trying to develop.

(Edit) I opened a bug in the tracker: [WFLY-6897] Replacing a disabled deployment destroys profile section of xml config - JBoss Issue Tracker

[mayerw01]

Maybe this is an issue with the admin console. Did you verify if the issue persists when you deploy the  application via cli like

deploy --force --disabled {pathToApplicatio}/myApplication.war

[ctomc]

Even better can you reproduce this on 10.1.0.CR1 what was released yesterday.

[mayerw01]

It looks like this had been solved now. At least I cannot reproduce this issue in version 10.1.0.CR1.

[brian.stansberry]

Yes, it's fixed in 10.1.0.CR1: [WFCORE-1577] After a full-replace-deployment operation a server on a hosts subsystem model is empty - JBoss Issue Track…