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

TCP connections are not closed for event based replication, if the credential are not configured correctly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 4.14.1, 5.3.0
    • Fix Version/s: 5.7.0
    • Component/s: None
    • Labels:
      None
    • Regression:
      Yes

      Description

      TCP connections get hang without releasing, when the replication config is setup with incorrect credential.

      This could cause some unresponsiveness to the instance/cluster performing this

      To reproduced the issue, follow the below steps:

      1. On Artifactory instance A, create local repo called adm-trash-local.
      2. On Artifactory instance B, create local repo called adm-trash-local.
      3. On instance A, set up replication from instance A to instance B of adm-trash-local, and enable event based replication. Set up invalid credential in the replication config.

      4. On instance A, use below command to list the opened TCP connections:
      lsof -p <pid_artiafctory> | grep TCP

      5. Deploy a file to instance A adm-trash-local.
      Below logs show up in artifactory.log because of wrong credential:

      2017-06-19 15:23:59,518 [http-nio-8081-exec-11] [ERROR] (o.a.a.r.c.l.e.ContextInitializingEventQueue:109) - Unable to initialize the replication event queue context for the repository 'adm-trash-local': Unable to identify target URL as an Artifactory instance: HTTP/1.1 401 Unauthorized
      2017-06-19 15:23:59,552 [http-nio-8081-exec-11] [ERROR] (o.a.a.r.c.l.e.ContextInitializingEventQueue:109) - Unable to initialize the replication event queue context for the repository 'adm-trash-local': Unable to identify target URL as an Artifactory instance: HTTP/1.1 403 Forbidden

      6. Use 'lsof' command to list the open TCP connection again on instance A again:
      Below connections are seen as new:

      java 15931 artifactor 206r IPv6 10607472 0t0 TCP camolx2056.mo.ca.am.ericsson.se:49370->arm-ha-vip2.mo.ca.am.ericsson.se:https (CLOSE_WAIT)
      java 15931 artifactor 210r IPv6 10605448 0t0 TCP camolx2056.mo.ca.am.ericsson.se:49366->arm-ha-vip2.mo.ca.am.ericsson.se:https (CLOSE_WAIT)

      You will notice that the new connections stay there for ever and are not being released afterward.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              mohammadt Mohammad Tibi
              Votes:
              7 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: