Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-26232

No CONNECT (outbound proxy) timeout configured for HTTP client

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: 3 - High
    • Resolution: Done
    • Affects Version/s: 6.23.23, 7.23.3
    • Fix Version/s: None
    • Component/s: Artifactory
    • Labels:
      None
    • Location:
      External

      Description

      Using a proxy with a remote repository, could cause request threads to get stuck when the proxy is not responding to CONNECT requests trying to connect to a remote repo.

      This happens due to the first thread trying to establish a connection with the proxy and is not able to, causing the the rest of the threads to wait forever for the the first request thread to complete (which will not happen unless the first connection is successful at some time in the future/the connection to the proxy is lost).

      • This issue was opened when a Docker remote tries to acquire a token to work with the remote repo's API, but can be applied to other repo types/outbound connections using a proxy and a caching mechanism that wait for the first request in the same manner

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            mattheww Matthew Wang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Sync Status

                Connection: RTFACT Sync
                RTMID-26233 -
                SYNCHRONIZED
                • Last Sync Date: