[
http://jira.codehaus.org/browse/MRM-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238074#action_238074
]
Brett Porter commented on MRM-1422:
-----------------------------------
can you try changing the proxy connector policy to "once" instead of "always"
for releases?
It seems like there's a problem in that "always" getting releases is only meant
to apply to the metadata, not the artifacts, but it may be rechecking.
> Slow proxy behavior with multiple proxies configured
> ----------------------------------------------------
>
> Key: MRM-1422
> URL: http://jira.codehaus.org/browse/MRM-1422
> Project: Archiva
> Issue Type: Improvement
> Components: remote proxy
> Affects Versions: 1.3.1
> Reporter: Philip K. Warren
> Fix For: 1.4
>
>
> I am seeing an issue with the remote proxying code that looks like it can
> cause a significant amount of unnecessary network traffic if multiple remote
> proxies have been configured.
> Here is an example of what is happening (after enabling logging in
> org.apache.maven.archiva.proxy package):
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Retrieving
> org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom from
> Central Repository if updated
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Artifact org.apache.maven.shared:maven-shared-io:1.1::pom not updated on
> repository "central".
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Path
> [org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom] is not
> part of defined whitelist (skipping transfer from repository [Java.net
> Repository for Maven 2]).
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Retrieving
> org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom from
> neo4j-public-repository if updated
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Artifact org.apache.maven.shared:maven-shared-io:1.1::pom not found on
> repository "neo4j".
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Retrieving
> org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom from
> JBoss if updated
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Artifact org.apache.maven.shared:maven-shared-io:1.1::pom not found on
> repository "jboss".
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Retrieving
> org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom from
> Codehaus Repository if updated
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Artifact org.apache.maven.shared:maven-shared-io:1.1::pom not found on
> repository "codehaus".
> DEBUG org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors -
> Exhausted all target repositories, artifact
> org.apache.maven.shared:maven-shared-io:1.1::pom not found.
> From the logs it appears that the first proxy repository returned that the
> resource is not out of date and exists on disk. However, this doesn't cause
> Archiva to stop looking for the repository - instead it looks for the "found"
> resource in all of the other repositories.
> The code in question is the loop in fetchFromProxies in
> DefaultRepositoryProxyConnectors.java. I think it should return immediately
> after finding that the resource hasn't been modified on the first proxy it
> finds (when catching NotModifiedException).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
