Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.1.4.CR1, 7.1.4.GA
Affects Version/s: 7.1.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.1.z.GA
Workaround Description:

Hide

Create or remove the non-existent server-groups

Show
Create or remove the non-existent server-groups
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/543, https://github.com/jbossas/wildfly-core-eap/pull/559

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

Configuring a host with:

<server name="server-one" group="main-server-group" auto-start="false"/>
<server name="server-two" group="main-server-group" auto-start="false">
<socket-bindings port-offset="150"/>
</server>

And no server-goup with that name in the domain.xml, the host starts and all management operations fail.

clones

WFCORE-3897 Host starts with server assigned to non-existent server group

Resolved

is incorporated by

JBEAP-14910 (7.1.z) Upgrade WildFly Core to 3.0.17.Final-redhat-1

Closed

Assignee:: Chao Wang

Reporter:: Teresa Miyar Gil (Inactive)

Tester:: Peter Mackay

QA Contact:: Peter Mackay

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2018/05/28 5:09 AM

Updated:: 2021/10/24 5:21 AM

Resolved:: 2018/07/10 10:16 PM