You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "bettydramit (JIRA)" <ji...@apache.org> on 2012/07/16 10:48:35 UTC
[jira] [Updated] (TS-1352) request wait for a long time....
[ https://issues.apache.org/jira/browse/TS-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
bettydramit updated TS-1352:
----------------------------
Description:
wget -S -O /dev/null -e http_proxy=127.0.0.1 http://www.test.com/aa26f5b2e2184dee342df987d5aa4d3e3b62067c21aea45e61961ea96618d550.html
--2012-07-16 16:44:15-- http://www.test.com/aa26f5b2e2184dee342df987d5aa4d3e3b62067c21aea45e61961ea96618d550.html
Connecting to 127.0.0.1:80... connected.
Proxy request sent, awaiting response...
the /var/log/messages
Jul 16 16:40:51localhost traffic_cop[5248]: (test) read timeout [180000 ]
Jul 16 16:40:51localhost traffic_cop[5248]: server heartbeat failed [1]
Jul 16 16:41:01localhost traffic_cop[5248]: server heartbeat succeeded
Jul 16 16:44:31localhost traffic_cop[5248]: (test) read timeout [180000 ]
Jul 16 16:44:31localhost traffic_cop[5248]: server heartbeat failed [1]
Jul 16 16:44:41localhost traffic_cop[5248]: server heartbeat succeeded
was:
wget -S -O /dev/null -e http_proxy=127.0.0.1 http://www.test.com/aa26f5b2e2184dee342df987d5aa4d3e3b62067c21aea45e61961ea96618d550.html
--2012-07-16 16:44:15-- http://www.test.com/aa26f5b2e2184dee342df987d5aa4d3e3b62067c21aea45e61961ea96618d550.html
Connecting to 127.0.0.1:80... connected.
Proxy request sent, awaiting response...
the /var/log/messages
Jul 16 16:40:51 localhost traffic_cop[5248]: (test) read timeout [180000 ]
Jul 16 16:40:51 localhost traffic_cop[5248]: server heartbeat failed [1]
> request wait for a long time....
> --------------------------------
>
> Key: TS-1352
> URL: https://issues.apache.org/jira/browse/TS-1352
> Project: Traffic Server
> Issue Type: Bug
> Affects Versions: 3.3.0
> Environment: centos 6.0 x86_64
> Reporter: bettydramit
>
> wget -S -O /dev/null -e http_proxy=127.0.0.1 http://www.test.com/aa26f5b2e2184dee342df987d5aa4d3e3b62067c21aea45e61961ea96618d550.html
> --2012-07-16 16:44:15-- http://www.test.com/aa26f5b2e2184dee342df987d5aa4d3e3b62067c21aea45e61961ea96618d550.html
> Connecting to 127.0.0.1:80... connected.
> Proxy request sent, awaiting response...
> the /var/log/messages
> Jul 16 16:40:51localhost traffic_cop[5248]: (test) read timeout [180000 ]
> Jul 16 16:40:51localhost traffic_cop[5248]: server heartbeat failed [1]
> Jul 16 16:41:01localhost traffic_cop[5248]: server heartbeat succeeded
> Jul 16 16:44:31localhost traffic_cop[5248]: (test) read timeout [180000 ]
> Jul 16 16:44:31localhost traffic_cop[5248]: server heartbeat failed [1]
> Jul 16 16:44:41localhost traffic_cop[5248]: server heartbeat succeeded
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira