[jira] [Commented] (TS-1483) Traffic Manager when autoconf fd > 32 will cause endless spins causing traffic_cop to kill server -- Backport 3.2.x

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652030#comment-13652030 ] 

ASF subversion and git services commented on TS-1483:
-----------------------------------------------------

Commit 547c0373a820eac8a32f542e62d094660c11e9d4 in branch refs/heads/3.2.x from Arno Töll <ar...@debian.org>
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=547c037 ]

Vote. +1 on TS-1483 and TS-1843

                
> Traffic Manager when autoconf fd > 32 will cause endless spins causing traffic_cop to kill server -- Backport 3.2.x
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: TS-1483
>                 URL: https://issues.apache.org/jira/browse/TS-1483
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Management
>    Affects Versions: 3.2.0
>            Reporter: Brian Geffon
>            Assignee: Brian Geffon
>             Fix For: 3.2.5
>
>         Attachments: WebIntrMain.patch
>
>
> WebIntrMain.cc uses a hard coded FD_SET Size of 32, so when the autoconf file descriptor is greater than 32 it will cause select to sleep forever since no timeout is specified. We had a few systems that would have continuous traffic_server restarts because they would (have a fd > 32) and would never accept the connection request for /synthetic.txt causing cop to kill mananger and server. But when Manager restarted is still got a high fd and it would happen again, while the whole time traffic_server is running just fine. This should be switched to FD_SETSIZE if available.
> Discovered by Thomas Jackson

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira