[
https://issues.apache.org/jira/browse/TS-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134279#comment-14134279
]
Sudheer Vinukonda commented on TS-2559:
---------------------------------------
It looks like this commit incorrectly places the error'ed server session back
into the pool, potentially impacting subsequent requests. We are seeing a
(slightly) increased POST failures with ats5 compared to ats4 and I am
wondering if this commit could be the reason. Coincidentally, it seems that
[~briang] also noticed this issue and provided a fix in TS-2991. Trying out
that fix in our network to see if it resolves the POST issue.
> active timeouts do not disconnect client sessions
> -------------------------------------------------
>
> Key: TS-2559
> URL: https://issues.apache.org/jira/browse/TS-2559
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 5.0.0
>
>
> If you set {{proxy.config.http.transaction_active_timeout_out}}, and a
> transaction aborts with a timeout when {{traffic_server}} is receiving the
> response body from the origin, the cache write is shut down but the client is
> left connected. There's no way for the client to handle this error except by
> timing our, so the right behavior is to shut down all the consumers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
