[
https://issues.apache.org/jira/browse/TS-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229174#comment-15229174
]
Eric Sproul commented on TS-4206:
---------------------------------
If I had to hazard a guess at what the issue might be, I'd say it was something
specific to an eventer change in 6.x that interacts badly with Solaris/illumos
ports. It seems like we're just losing track of the session and never handling
it. This might explain why we've seen it and (apparently) no one else has, as
there probably aren't many Solaris/illumos ATS users out there.
> Stalled connections show a client request but no HTTP response
> --------------------------------------------------------------
>
> Key: TS-4206
> URL: https://issues.apache.org/jira/browse/TS-4206
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, HTTP
> Reporter: Eric Sproul
> Assignee: Bryan Call
> Priority: Blocker
> Labels: regression
> Fix For: 6.2.0
>
>
> Have been discussing this one on IRC but wanted to capture everything here
> since it seems like a fairly serious issue. Since upgrading from 5.3.2 to
> 6.1.1 we have witnessed connections that, from the client perspective, seem
> to stall after the client sends the request. TS logs the connection only
> after it seemingly hits {{proxy.config.net.default_inactivity_timeout}} (5
> minutes), but logs a response code of 000, despite the presence of a request
> (e.g. GET with a request URL logged).
> For the time being we have failed back to 5.3.2 but I was able to capture a
> sample of this situation in the slow log. [This
> paste|http://apaste.info/ds1] shows the slow log as well as the corresponding
> squid.blog entry (default format).
> This issue feels similar to TS-3456 but we are not using tunneling, though we
> are using SSL/TLS in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
