[
https://issues.apache.org/jira/browse/TS-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293903#comment-14293903
]
Bryan Call commented on TS-3119:
--------------------------------
Git commit history:
commit e5069f1b6249bcd62f5bf1a425ed16926ac2bbba
Author: Kang Li <[email protected]>
Date: Wed Oct 29 17:04:03 2014 -0700
TS-3119: add SO_LINGER socket option support
The timeout should be 0 if we turn on SO_LINGER option as we are
using non-blocking socket. I have tried a non-zero timeout, but the
setsockopt failed.
If we add a new sock option
static unit32_t const SOCK_OPT_LINGER_ON = 4;
Then we could configure
proxy.config.net.sock_option_flag_in
proxy.config.net.sock_option_flag_out
to make client connection or server connection LINGER for 0 ms if
needed.
> Add option to support SO_LINGER to origin server
> ------------------------------------------------
>
> Key: TS-3119
> URL: https://issues.apache.org/jira/browse/TS-3119
> Project: Traffic Server
> Issue Type: New Feature
> Components: Network
> Reporter: kang li
> Assignee: James Peach
> Fix For: 5.2.0
>
> Attachments: add_so_linger_as_option.diff, linger.diff
>
>
> When install ATS and apache in the same box to do SSL termination. We saw
> port exhaustion, performance drop and request missing through ATS.
> Before migration we are using stunnel to do SSL termination. There were no
> such problem. After investigation we found add SO_LINGER option to origin
> could resolve these problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
