[ https://issues.apache.org/jira/browse/TS-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168085#comment-14168085 ]
kang li commented on TS-3119: ----------------------------- Hi [~jpe...@apache.org], 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 {code} static unit32_t const SOCK_OPT_LINGER_ON = 4; {code} Then we could configure {code} proxy.config.net.sock_option_flag_in proxy.config.net.sock_option_flag_out {code} to make client connection or server connection LINGER for 0 ms by need. > 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: Improvement > Components: Network > Reporter: kang li > Fix For: 5.2.0 > > Attachments: 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)