[jboss-jira] [JBoss JIRA] (WFLY-8762) WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar commented on WFLY-8762:
-----------------------------------

after the proposed PR this is what happens when you try to remove worker

{noformat}
[standalone at localhost:9990 /] /subsystem=io/worker=default:remove
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0367: Cannot remove capability 'org.wildfly.io.worker.default' as it is required by other capabilities:
capability 'org.wildfly.undertow.listener.https' requires it for attribute 'worker' at address '/subsystem=undertow/server=default-server/https-listener=https'
capability 'org.wildfly.undertow.listener.default' requires it for attribute 'worker' at address '/subsystem=undertow/server=default-server/http-listener=default'
capability 'org.wildfly.remoting.endpoint' requires it for attribute 'worker' at address '/subsystem=remoting/configuration=endpoint'",
    "rolled-back" => true
}
{noformat}

> WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-8762
>                 URL: https://issues.jboss.org/browse/WFLY-8762
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>            Reporter: Brian Stansberry
>            Assignee: Tomaz Cerar
>
> This makes it hard to remove or rename the 'default' worker (e.g. as part of doing performance tuning), because the requirement for that worker isn't shown in standalone.xml. Since there's no capability ref failure, boot proceeds to RUNTIME, ServletContainerService can't start but a whole lot of others can't start as well. So there's a lot of noise that obscures the issue.



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