[jira] Commented: (TS-382) socket option "cleanup" (and bug fixes)

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

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

Leif Hedstrom commented on TS-382:
----------------------------------

Comment #10 (from leif):

A few more things that we should fix:

1) We set TCP_NODELAY and SO_KEEPALIVE on various sockets "hardcoded" (i.e. it does not honor the config
settings).

2) There are a few cases where we'll actually end up calling setsockopt() multiple times on the same socket.

I'm adding in some Debug() stuff (with a tag "socket") to help debug this.



> socket option "cleanup" (and bug fixes)
> ---------------------------------------
>
>                 Key: TS-382
>                 URL: https://issues.apache.org/jira/browse/TS-382
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Leif Hedstrom
>
> This is a bug moved from Y! Bugzilla, I'm posting the original bug description and a few comments separately. Note that the bug description is fairly limited, but while looking at this code, I noticed a lot of oddities with the "socket option" support (lots of hardcoded stuff, and most of it is not configurable).
> Note that the original bug should have been fixed already in Apache TS, but the other comments are still applicable.
> From Bugzilla (posted by Leif):
> We have two socket option config options in records.config:
> proxy.config.net.sock_option_flag_in
> proxy.config.net.sock_option_flag_out
> With accept thread enabled, at least the _in option isn't honored. There are possibly other cases in UnixNetAccept.cc
> that we don't honor these flags either.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.