You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/04/17 20:21:25 UTC

[jira] [Updated] (TS-4346) Requests that hit conneciton limits (max_origin_connections, etc.) incur a hard coded latency hit

     [ https://issues.apache.org/jira/browse/TS-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-4346:
------------------------------
    Fix Version/s: sometime

> Requests that hit conneciton limits (max_origin_connections, etc.) incur a hard coded latency hit
> -------------------------------------------------------------------------------------------------
>
>                 Key: TS-4346
>                 URL: https://issues.apache.org/jira/browse/TS-4346
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Thomas Jackson
>             Fix For: sometime
>
>
> example: https://github.com/apache/trafficserver/blob/master/proxy/http/HttpSM.cc#L4741
> Ideally this would instead put the transaction in some queue to be processed, such that the transaction could be resumed as soon as a connection becomes available.



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