[jira] [Updated] (TS-4430) Timeout settings made via API calls don't always override configured values

["Alan M. Carroll (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan M. Carroll updated TS-4430:
--------------------------------
    Fix Version/s:     (was: 7.0.0)
                   7.1.0

> Timeout settings made via API calls don't always override configured values
> ---------------------------------------------------------------------------
>
>                 Key: TS-4430
>                 URL: https://issues.apache.org/jira/browse/TS-4430
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>            Reporter: Oliver Goodman
>            Priority: Minor
>             Fix For: 7.1.0
>
>
> Settings changed via calls to TSHttpTxnActiveTimeoutSet and TSHttpTxnNoActivityTimeoutSet can only be used to set shorter timeouts than those set by configuration. If longer timeouts are set, the configured timeouts will continue to apply.
> This is due to the fact that timeouts have to be set on two NetVConnection objects, of type PluginVC and UnixNetVConnection. Code in HttpSM is only updating the former to match API settings, but a timeout occurring on either object terminates the transaction.



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