[
https://issues.apache.org/jira/browse/TS-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241909#comment-15241909
]
Eric Sproul commented on TS-4206:
---------------------------------
[~bcall] I think I have reproduced the issue in a dev environment. Here is the
squid log and the slow log for this request (lines wrapped for clarity):
{code}
1460667286.245 900263 x.x.x.x ERROR_UNKNOWN(90)/000 0 GET <redacted> - EMPTY/- -
{code}
{code}
[Apr 14 20:54:46.245] Server {0x16} ERROR: <HttpSM.cc:6820 (update_stats)> [49]
Slow Request:
client_ip: x.x.x.x:60916 url: <redacted>
status: 0 unique id: redirection_tries: 0 bytes: 0 fd: 0
client state: 0 server state: 0 ua_begin: 0.000 ua_first_read: 0.000
ua_read_header_done: -1.000
cache_open_read_begin: -1.000 cache_open_read_end: -1.000
dns_lookup_begin: -1.000 dns_lookup_end: -1.000
server_connect: -1.000 server_first_read: -1.000 server_read_header_done:
-1.000
server_close: -1.000 ua_close: -1.000 sm_finish: 900.264 plugin_active: -1.000
plugin_total: -1.000
{code}
> 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)
