Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-27794

Check Status thread does not detect changes to HTTP Proxy server configuration

    XMLWordPrintable

    Details

    • Story Points:
      3
    • Sprint:
      NXRM MadMax Sprint 21, NXRM MadMax Sprint 22

      Description

      1. Misconfigure HTTP Proxy server in NXRM to an IP address and port that can't be connected to.
      2. Send a request inbound to a proxy repo.
      3. After outbound request times out because HTTP proxy server address cannot be reached, proxy repo will become auto blocked. A "Check Status" thread launches in the background to periodically check the remote for unblocking.
      4. Admin changes port of HTTP proxy server in NXRM to correct port.
      5. Check Status thread continues checking remote at old port and does not ever detect that HTTP proxy server port has been changed.

      The only way to escape this rogue Check Status thread checking wrong port is to restart NXRM.

      Expected

      The background Check Status thread should update itself with any HTTP Proxy server config changes that are made, before continuing to send the next new request.

        Attachments

          Activity

            People

            Assignee:
            vgrab Vladimir Grab
            Reporter:
            plynch Peter Lynch
            Last Updated By:
            Vladimir Grab Vladimir Grab
            Team:
            NXRM - Mad Max
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title