[
https://issues.jboss.org/browse/WFLY-12019?page=com.atlassian.jira.plugin...
]
Bartosz Spyrko commented on WFLY-12019:
---------------------------------------
[~brian.stansberry] as far as I can tell, once the WFCORE-4462 and WFLY-12047 are fixed,
the whole resource tree under Host should be supporting allow-resource-service-restart and
have restartLevel of RESTART_RESOURCE_SERVICES, so that should address the original
issue.
I guess the HostRemove should check if resource restart is allowed before removing
services - apart from there is there any further improvement that should be made?
Is that an acceptable solution or should the host remove operation be changed to
ReloadRequiredRemoveStepHandler like you mentioned?
Cannot remove a undertow server resource at one time
----------------------------------------------------
Key: WFLY-12019
URL:
https://issues.jboss.org/browse/WFLY-12019
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 16.0.0.Final
Reporter: Bartosz Spyrko
Assignee: Bartosz Spyrko
Priority: Major
Cannot remove a server attribute.
{noformat}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server:remove()
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0171: Removing services has lead
to unsatisfied dependencies:
Service jboss.undertow.server.default-server.default-host was depended upon by service
jboss.undertow.server.default-server.default-host.filter-ref.x-powered-by-header, service
jboss.undertow.server.default-server.default-host.location.
/, service
jboss.undertow.server.default-server.default-host.filter-ref.server-header",
"rolled-back" => true,
"response-headers" => undefined
}
{noformat}
However, it can be removed executing same command again.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)