[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-355) Allow connector to not define maximum capacity (e.g. Undertow listener)

[Radoslav Husar (JIRA)]

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

Radoslav Husar commented on MODCLUSTER-355:
-------------------------------------------

PR: https://github.com/modcluster/mod_cluster/pull/39
                
> Allow connector to not define maximum capacity (e.g. Undertow listener)
> -----------------------------------------------------------------------
>
>                 Key: MODCLUSTER-355
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-355
>             Project: mod_cluster
>          Issue Type: Feature Request
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>             Fix For: 1.3.0.Alpha1
>
>
> See WFLY-1888.
> In WF we are wrapping Undertow listener with Connector interface. However, with all the async processing the maximum capacity does not represent busyness correctly. 
> I am going to add support for the connector to return "-1" that indicates to mod_cluster that this connector does not define maximum number of threads and leave the load calculation to capacity instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira