Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.0.4.CR1, 7.0.4.GA
Affects Version/s: 7.0.2.GA
Component/s: Management, Server
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.0.4.GA
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/290

Sprint:
EAP 7.0.4

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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

clones

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

Closed

is incorporated by

JBEAP-6603 (7.0.z) Upgrade WildFly Core from 2.1.9.Final-redhat-1 to 2.1.10.Final

Closed

relates to

WFLY-6897 Replacing a disabled deployment destroys profile section of xml config

Closed

Assignee:: Chao Wang

Reporter:: Marcus Carvalho (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2016/10/24 3:42 PM

Updated:: 2024/09/13 4:00 PM

Resolved:: 2016/11/08 9:00 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates