trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Peach <jpe...@apache.org>
Subject Re: traffic server no response while reading body.
Date Fri, 11 Mar 2016 16:16:42 GMT

> On Mar 11, 2016, at 1:50 AM, feng D <fengidri@gmail.com> wrote:
> 
> I found that traffic server just output about half of the body to client, then no response.
And left the tcp connect alive.
> 
> And I found that just happens when the number of the connection is up to 8000.
> 
> like this:
> *********************************************************
> # ss -n sport = :80 |wc -l
> 7822
> *********************************************************
> 
> curl download is like:
> *********************************************************************************
> # curl http://domain.com/upload/plug-ins/mb20160308.apk -x  192.168.250.5:80 -o /dev/null
-v
> * Hostname was NOT found in DNS cache
> *   Trying 192.168.250.5...
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
>                                  Dload  Upload   Total   Spent    Left  Speed
>   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Connected
to 192.168.250.5 (192.168.250.5) port 80 (#0)
> > GET http://domain.com/upload/plug-ins/mb20160308.apk HTTP/1.1
> > User-Agent: curl/7.35.0
> > Host: domain.com
> > Accept: */*
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.1 200 OK
> * Server ATS/4.2.2 is not blacklisted
> < Server: ATS/4.2.2
> < Date: Tue, 08 Mar 2016 11:40:34 GMT
> < Content-Type: application/vnd.android.package-archive
> < Content-Length: 838197
> < Last-Modified: Tue, 08 Mar 2016 11:40:31 GMT
> < Accept-Ranges: bytes
> < ETag: W/"838197-1457437231000"
> < Expires: Wed, 16 Mar 2016 02:06:49 GMT
> < Cache-Control: max-age=656775
> < Age: 248321
> < Via: http/1.1 ats (ApacheTrafficServer/4.2.2 [cHs f ])
> < Proxy-Connection: keep-alive
> <
> { [data not shown]
>  43  818k   43  352k    0     0   1200      0  0:11:38  0:05:00  0:06:38     0* transfer
closed with 477366 bytes remaining to read
>  43  818k   43  352k    0     0   1200      0  0:11:38  0:05:00  0:06:38     0
> * Closing connection 0
> curl: (18) transfer closed with 477366 bytes remaining to read

Traffic Server closed the connection. Take a look at the logs; maybe it told you what went
wrong?

J


Mime
View raw message