Repository Replication allows replicating the content of repositories from one Artifactory instance to another using Pull or Push replication strategies. In order for the replication to work, each instance of Artifactory that participates in the replication needs to have a separate and unique Artifactory license. In some occasions, users may encounter an error indicating that same license is being used in the source instance (where the replication is triggered from) and the target Artifactory instance, a setup that is not supported. The error will look similar to this:
The above may indicate that once of the instances or nodes share at least one license. To confirm that all the licenses are different, you may navigate to the $JFROG_HOME/artifactory/etc/artifactory directory and review the following files:
For a single node setup, make sure that the source and target licenses in the artifactory.license file are unique. For an HA setup, the artifactory.cluster.license will include a few license keys, separated by new lines, depending on the number of nodes in the cluster. No license key should be identical across the nodes in the cluster as well as the nodes in the remote Artifactory cluster.
Note: Each Artifactory server must have its own unique license regardless of replication.
2023-08-23T09:50:15.531Z [jfrt ] [ERROR] [a4875ef5aa4d0405] [o.a.a.r.c.p.e.EventQueue:131 ] [4d0405|art-exec-4843] - Unable to initialize the replication event queue context for the repository 'example-repo-local': Replication between same-license servers is not supported.
The above may indicate that once of the instances or nodes share at least one license. To confirm that all the licenses are different, you may navigate to the $JFROG_HOME/artifactory/etc/artifactory directory and review the following files:
- artifactory.lic for a single node setup.
- artifactory.cluster.license for an HA setup.
For a single node setup, make sure that the source and target licenses in the artifactory.license file are unique. For an HA setup, the artifactory.cluster.license will include a few license keys, separated by new lines, depending on the number of nodes in the cluster. No license key should be identical across the nodes in the cluster as well as the nodes in the remote Artifactory cluster.
Note: Each Artifactory server must have its own unique license regardless of replication.