[jira] [Commented] (TS-4342) Connections queued when hitting `proxy.config.http.origin_max_connections` don't honor order

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241615#comment-15241615 ] 

ASF subversion and git services commented on TS-4342:
-----------------------------------------------------

Commit fa1bb2951475ddb92e624fde011843a9a905c603 in trafficserver's branch refs/heads/master from [~jacksontj]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=fa1bb29 ]

TS-4342 Add tests for queued/max connections in addition to base tests


> Connections queued when hitting `proxy.config.http.origin_max_connections` don't honor order
> --------------------------------------------------------------------------------------------
>
>                 Key: TS-4342
>                 URL: https://issues.apache.org/jira/browse/TS-4342
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Thomas Jackson
>            Assignee: Thomas Jackson
>
> As of today when you hit `proxy.config.http.origin_max_connections` requests are queued waiting for an available connection to origin. Today this is done by simply [rescheduling 100ms in the future|https://github.com/apache/trafficserver/blob/master/proxy/http/HttpSM.cc#L4756]. Ideally this would honor the order with which the requests came in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)