[
https://issues.apache.org/jira/browse/TS-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jackson updated TS-4343:
-------------------------------
Fix Version/s: sometime
> When ATS hits `proxy.config.http.origin_max_connections`, the requests queued
> will not abort even if client aborts
> ------------------------------------------------------------------------------------------------------------------
>
> Key: TS-4343
> URL: https://issues.apache.org/jira/browse/TS-4343
> Project: Traffic Server
> Issue Type: Bug
> Components: Network
> Reporter: Thomas Jackson
> Assignee: Thomas Jackson
> Fix For: sometime
>
>
> While testing my patch for TS-4341 I've noticed that once a request is queued
> waiting for max connections, ATS will not abort the request even if the
> client has completely disconnected. It seems that ATS is only setting up a
> consumer of the UA tunnel if there is a post body-- and as such we never see
> the socket close on us. Still digging into this some, but this seems like a
> problem ;)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
