archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas de loof" <>
Subject cache-failure enhancement
Date Fri, 21 Dec 2007 09:57:21 GMT

The cache-failure option on proxy connectors doesn't seem to act as user
(and myself) may expect.

A failing (404) artifact request is not cached, as any network errors.

This has the side effect that :

1. network issues to access proxied repositories can make archiva unusable
2. archiva performance can get slow when using downloadSources form IDE
plugins, as many artifacts have no source attached and any user launching
mvn eclipse:eclipse will make archiva fetch it's proxyConnectors

I suggest the following changes :

- in DefaultRepositoryProxyConnectors, first look in UrlCache for previously
failed request, and skip fetching the proxy if found
- add 404 (ArtifactNotFoundException) errors to the failureCache

The cache is also hard-configured in plexus descriptors. Maybe some user
would like to have an admin command / configuration to flush it and/or the
the time-to-live attribute.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message