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

Susan Hinrichs commented on TS-3905:
------------------------------------

[~zwoop] you are right.  TS-3312 addresses this issue.  I filed this bug based 
on code inspection.  It didn't appear that we were using the 
keep_alive_timeout_out parameter.  But reviewing this bug, I see that we are 
using that parameter although in kind of an odd path to enable parameter 
override.

I'll verify it runs for my scenario Monday, but I assume if it meets LinkedIn's 
needs it will also work for me, so I'm closing as a duplicate.

> proxy.config.http.keep_alive_no_activity_timeout_out is not used
> ----------------------------------------------------------------
>
>                 Key: TS-3905
>                 URL: https://issues.apache.org/jira/browse/TS-3905
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP
>            Reporter: Susan Hinrichs
>            Assignee: Susan Hinrichs
>             Fix For: 6.1.0
>
>
> The keep_alive_no_activity_timeout_in is set correctly on the 
> HttpClientSession when the transaction releases it.  The client session is 
> then hanging out until the next transaction appears, and the 
> keep_alive_no_activity_timeout_in should apply instead of the 
> transaction_no_activity_timeout_in.
> For the server session side, the keep_alive_no_activity_timeout_out and 
> transaction_no_activity_timeout_out should apply.  The 
> keep_alive_no_activity_timeout_out does get set correctly when the server 
> session is attached to the client session to timeout via the 
> HttpClientSession::attach_server_session_method().
> But in ServerSessionPool::releaseSession, the following is called
> {code}
> ss->get_netvc()->set_inactivity_timeout(ss->get_netvc()->get_inactivity_timeout());
> {code}
> My reading is that this will reset the inactivity timeout of the server 
> session to whatever it was last set to.  Instead it should set the inactivity 
> timeout to keep_alive_no_activity_timeout_out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to