[jboss-jira] [JBoss JIRA] (WFLY-8821) Operation removing http-connector requires full server reload but does not change the server state accordingly

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410574#comment-13410574 ] 

Brian Stansberry commented on WFLY-8821:
----------------------------------------

[~mjurc] What's the symptom that indicates the connector is not removed?  The handler for the remove op is quite straightforward and is removing the service. 

I'm not an expert in this but it looks like removing the service is not something that would result in any existing connections/channels being closed.

> Operation removing http-connector requires full server reload but does not change the server state accordingly
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-8821
>                 URL: https://issues.jboss.org/browse/WFLY-8821
>             Project: WildFly
>          Issue Type: Bug
>          Components: Remoting
>            Reporter: Michal Jurc
>            Assignee: David Lloyd
>
> Removing a {{http-connector}} with {{allow-resource-service-restart}} set to {{true}} will yield the following result:
> {code}{
>     "operation" => "remove",
>     "address" => [
>         ("subsystem" => "remoting"),
>         ("http-connector" => "ejb3-tests")
>     ],
>     "operation-headers" => {"allow-resource-service-restart" => true}
> }
> {"outcome" => "success"}{code}
> However, the removal of {{http-connector}} will only register after full server reload.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)