Artifactory Pro是否支持Event-based push？配置后为何未即时复制？

Let's break down what's happening here: you've set up push replication between two repositories in Artifactory Pro 5.9.0 rev 50900900, enabled "Enable Event Replication" as documented, but artifacts only show up in the target repo after the 5-minute scheduled replication kicks in. No event-driven replication entries are showing up in your logs either—frustrating, I know.

Here are targeted checks and fixes tailored to your Artifactory version:

• Double-check your replication config's fine print
  First, confirm you're using Push Replication (not pull) and that the "Enable Event Replication" checkbox is actually saved correctly. In 5.9.0's UI, sometimes the setting can look checked but not persist if you don't re-save the config after making changes. Also, verify the target repository exists and is reachable (if it's a remote instance, test connectivity from your Artifactory server to the target).

• Dig into the right logs for event activity
  Don't just look at the main replication logs—check artifactory-event.log and artifactory-request.log in your Artifactory logs directory. Event-based replication relies on Artifactory catching the artifact upload event first; if these logs don't show an event firing when you upload a test artifact, the problem is with the event system itself. For 5.9.0, there's a known quirk where very large uploads might not trigger events immediately—test with a tiny text file (1KB) to rule this out.

• Ensure repository types and filters play nice
  Event-based replication has compatibility rules: for example, you can't replicate from a virtual repo to a remote repo directly. Confirm both source and target repos are compatible (local-to-local, local-to-virtual, etc.). Also, check for hidden filters—even if you didn't set explicit include/exclude patterns, double-check those fields in the replication config. Empty fields should mean all artifacts are included, but sometimes default filters can sneak in and block replication.

• Look for 5.9.0-specific bugs and patches
  Artifactory 5.9.0 has a few known issues with event replication. If your instance is under heavy load, event processing can get backed up, making it seem like replication isn't instant. Check artifactory-service.log for warnings about "event dispatcher" or "replication queue". Also, the base 5.9.0 release (rev 50900900) has some fixes in later 5.9.x patches—consider updating to the latest patch for 5.9.x if possible, as some event replication triggers were corrected in those updates.

• Test replication manually to isolate the issue
  To figure out if the problem is with event triggering or the replication itself, trigger a replication manually via the API. Run this command (swap in your instance's credentials and repo names):

  curl -u your-username:your-password -X POST "http://your-artifactory-url/artifactory/api/replications/execute/[source-repo-name]-[target-repo-name]"
  

  If this manual replication works right away, then the issue is definitely with the event triggering system, not the replication mechanism.

• Check the "Async Event Replication" system setting
  Head to Admin > Advanced > System Settings and look for "Async Event Replication". If this is enabled, event replication runs in the background, which might add a small delay—but not 5 minutes. If it's disabled, replication should be near-instant. Toggle this setting, save, and test again to see if it changes anything.

内容的提问来源于stack exchange，提问作者zystem