Issue Analysis:

ARTIFACTORY: Troubleshooting Timeout Errors When Resolving Non-Existing Artifacts in a Virtual Repository with an Invalid Remote Repository

AuthorFullName__c
David Shin, Melissa McKay
articleNumber
000005953
FirstPublishedDate
2024-01-04T12:02:14Z
lastModifiedDate
2025-05-21
VersionNumber
2
The delay of 15-30 seconds before receiving a 404 error for non-existing artifacts is due to the Socket Timeout setting in the remote repository, which is set to a default of 15 seconds. This extended period allows for the client to wait for a response before receiving the error.

Furthermore, the issue is likely to occur intermittently, approximately every 30 minutes, because of the Missed Retrieval Cache Period setting, which is currently set to 30 minutes.

To expedite the verification or replication of the issue, it is recommended to set the Missed Retrieval Cache Period to 0.