Mismatch of timeouts used by proxypoller and passive proxy

XMLWordPrintable

    • Type: Problem report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: 3.0.11rc1, 3.2.8rc1, 3.4.2rc1
    • Component/s: Proxy (P), Server (S)

      Server's proxypoller process sets CONFIG_TRAPPER_TIMEOUT for the whole message exchange while passive proxy uses CONFIG_TIMEOUT per message.

      With default values of 300 and 3 seconds for CONFIG_TRAPPER_TIMEOUT and CONFIG_TIMEOUT respectively, this behaviour causes more network errors from proxy's perspective than it should and wastes some server resources.

            Assignee:
            Unassigned
            Reporter:
            Glebs Ivanovskis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: