Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-4430

Timeout settings made via API calls don't always override configured values

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 7.1.0
    • Component/s: TS API
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              oag Oliver Goodman
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: