[
http://jira.codehaus.org/browse/MRM-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154908#action_154908
]
Andrew Heald commented on MRM-1012:
-----------------------------------
Hmmm, I was totally mistaken about the source of this problem. The blacklists
ARE being correctly honoured. Might I suggest, however, that you apply the
following simple patch. I suspect the extra default log file overhead will be
worth it when admins want to make sure that their white/black lists are correct.
Index:
src/main/java/org/apache/maven/archiva/proxy/DefaultRepositoryProxyConnectors.java
===================================================================
---
src/main/java/org/apache/maven/archiva/proxy/DefaultRepositoryProxyConnectors.java
(revision 719210)
+++
src/main/java/org/apache/maven/archiva/proxy/DefaultRepositoryProxyConnectors.java
(working copy)
@@ -556,7 +556,7 @@
// Path must belong to whitelist.
if ( !matchesPattern( remotePath, connector.getWhitelist() ) )
{
- log.debug( "Path [" + remotePath +
+ log.info( "Path [" + remotePath +
"] is not part of defined whitelist (skipping transfer
from repository [" +
remoteRepository.getRepository().getName() + "])." );
return null;
@@ -566,7 +566,7 @@
// Is target path part of blacklist?
if ( matchesPattern( remotePath, connector.getBlacklist() ) )
{
- log.debug( "Path [" + remotePath + "] is part of blacklist
(skipping transfer from repository [" +
+ log.info( "Path [" + remotePath + "] is part of blacklist
(skipping transfer from repository [" +
remoteRepository.getRepository().getName() + "])." );
return null;
}
It turns out our performance degradation was caused by the use of
<updatePolicy>always</updatePolicy> in our repository configs. We used to have
several repositories listed to cover both internal and external repos. On
installing Archiva 1.1.3 I created a single repository group with the same URL
and name as the original main internal repo. This was so that any developer
that didn't properly update settings.xml would still get builds just as before.
As things were the update policy was applied only for the internal repo. So the
change to a single repo group ended up applying it across the board! The policy
has been removed altogether now. We'll use the Maven -U command line switch to
force a full update until we think up a better way of dealing with this.
Perhaps we should have two groups named something like "catlin" and "outside".
I hope that makes sense. I'll try to find a place to add a note about this sort
of thing on the wiki.
Meanwhile, I'll consider if this is grounds for closing this Jira.
> Delays in searching proxies due to blacklist not being honoured
> ---------------------------------------------------------------
>
> Key: MRM-1012
> URL: http://jira.codehaus.org/browse/MRM-1012
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.3
> Environment: Windows and jdk1.5.0_16-win32
> Reporter: Andrew Heald
> Priority: Critical
> Fix For: 1.2
>
>
> All my proxy connectors have com/catlin/** as a blacklist item which should
> mean that our own internal artifacts are not searched for through our proxy.
> However, the logs show this is happening, and this is slowing down or builds
> considerably. Is this an Archiva bug or a config bug on my part?
> 2008-11-19 11:45:53,569 [btpool0-4] INFO
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> not attempted on
> http://snapshots.repository.codehaus.org//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> : NO to fetch, check-failures detected previous failure on url:
> http://snapshots.repository.codehaus.org//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> 2008-11-19 11:45:53,569 [btpool0-4] INFO
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> not attempted on
> http://mirrors.ibiblio.org/pub/mirrors/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> : NO to fetch, check-failures detected previous failure on url:
> http://mirrors.ibiblio.org/pub/mirrors/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> 2008-11-19 11:45:53,569 [btpool0-4] INFO
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> not attempted on
> http://junitee.sourceforge.net/repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> : NO to fetch, check-failures detected previous failure on url:
> http://junitee.sourceforge.net/repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> 2008-11-19 11:45:53,569 [btpool0-4] INFO
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> not attempted on
> http://repo1.maven.org/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> : NO to fetch, check-failures detected previous failure on url:
> http://repo1.maven.org/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> 2008-11-19 11:45:53,569 [btpool0-4] INFO
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> not attempted on
> http://people.apache.org/repo/m2-snapshot-repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> : NO to fetch, check-failures detected previous failure on url:
> http://people.apache.org/repo/m2-snapshot-repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> 2008-11-19 11:45:53,569 [btpool0-4] INFO
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> not attempted on
> http://repository.jboss.com/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> : NO to fetch, check-failures detected previous failure on url:
> http://repository.jboss.com/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> 2008-11-19 11:45:53,569 [btpool0-4] INFO
> org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer
> not attempted on
> http://gwt-maven.googlecode.com/svn/trunk/mavenrepo//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
> : NO to fetch, check-failures detected previous failure on url:
> http://gwt-maven.googlecode.com/svn/trunk/mavenrepo//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
--
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
