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

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFLY-8762:
----------------------------------------

Why doesn't your new capability show up in that failure?  I was getting that message originally, and quickly fixed those three since the failure message told me what to fix reasonably simply, but then the websocket one was still failing the boot.

I fear the problem is those websocket attributes are not configured but rather have default values, and we're not registering the requirement.

> 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)