OK thanks, I figured out what's going on. The checksum was failing for http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.p om
Testing confirms that it seems the checksums in the central repo are wrong. I manually ran md5 and sha1 sums on that file, and they do not match the sums stored in central. By comparison, the pom for 2.0.7 does not have this problem. Having confirmed this, if I could beg your indulgence for a couple of followup questions: 1) You said you didn't have this problem... I presume you have checksumming set to 'ignore' or 'fix' in Archiva? 2) Is a 404 really the only error we get on this problem? This is the same thing you'd get for a completely nonexistent artifact, it's kind of misleading. 3) (Rhetorical question) WTF is up with Maven central having bad checksums for Maven's own artifacts, and how can I be the first one to notice this? Did I make some mistake, or is everyone except me ignoring checksums? -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, February 29, 2008 10:49 AM To: [EMAIL PROTECTED] Subject: Re: Archiva selectively failing to proxy one particular artifact the log configuration files are in /apps/archiva/webapp/WEB-INF/classes/log4j.xml On 01/03/2008, Brown, Carlton <[EMAIL PROTECTED]> wrote: > How/where/what are the options to manipulate Archiva logging? > > It's on Windoze, probably not a permissions problem... I haven't done > anything special to that particular directory, and there are scores of > other artifacts being proxied and served without issue. Just one day > Maven started requesting the 2.0.6 pom for whatever reason, and > Archiva refused to proxy that artifact (and only that artifact). > > Archiva also proxied successfully the Maven pom for 2.0.5 or 2.0.7 > (which was requested by Maven 2.0.8 for reasons known only to itself, > which I'll need to investigate later). > > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Thursday, February 28, 2008 5:16 PM > To: [EMAIL PROTECTED] > Subject: Re: Archiva selectively failing to proxy one particular > artifact > > what about permissions problems? anything in the logs (may need to > turn up the level a bit)? > > The other thought is whether the database has something in it that > causes it not to work, but I don't think it's consulted first. > > I'm out of other ideas... really quite strange. > > - Brett > > On 29/02/2008, Brown, Carlton <[EMAIL PROTECTED]> wrote: > > It populates just an empty 2.0.6 directory. The behavior is the > same > > > whether that dir is pre-existing or not. I guess I could try > > installing that artifact by hand and see what happens. > > > > I've also tried restarting tomcat as well. I'm not sure how I > might > go about restoring the state other than that. > > > > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: > Thursday, February 28, 2008 4:45 PM > To: > [EMAIL PROTECTED] > Subject: Re: Archiva selectively > failing to proxy one particular > artifact > > it works for me, so > there must be a state problem rather than a bug > in the proxying > related to that artifact. > > > > Do you have any content for that version in the managed repository? > > > > - Brett > > > > On 29/02/2008, Brown, Carlton <[EMAIL PROTECTED]> wrote: > > > I have a strange problem where an Archiva instance absolutely > > refuses > to retrieve one particular artifact from central under any > > > circumstances... > > > it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've > verified > > > that the instance can retrieve other artifacts, in fact > > > maven-2.0.5.pom retrieves just fine, as well as other randomly > > selected jars and pom > > > files. It's only maven-2.0.6.pom that it fails on. I also > verified > > > that the file is in fact on maven central. > > > > > > When I say I'm testing it, I mean that I'm pointing a browser > to > the > > > archiva URL designating an artifact that is not yet > proxied, for > > > > example > > > > http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/ > > > ma ven-2.0.6.pom which returns a 404 error message. > > > > > > Also, I don't know if this is related or not, but the 404 > message > > > > displays a munged, invalid URL: > > > The following resource does not exist: > > > > > > > > > http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom > > > > > > > > > <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.po > > > m> > > > > > > > > > Notice that the the context string "archiva" doesn't appear in > the > > displayed URL, and neither does the repository name "myrepo". > But > > > since this behavior is reproducible with other well-formed > URL's > for > > > nonexistent artifacts, this may not be related > to my problem at all. > > > > > > Thanks in advance... > > > > > > > > > > > > > > > ----------------------------------------- > > > ==================================================== > > > This message contains PRIVILEGED and CONFIDENTIAL information > > that > is intended only for use by the named recipient. If you are > > not the > named recipient, any disclosure, dissemination, or > action > based on > the contents of this message is prohibited. In > such case > please > notify us and destroy and delete all copies > of this transmission. > > > Thank you. > > > ==================================================== > > > > > > -- > > Brett Porter > > Blog: http://blogs.exist.com/bporter/ > > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > ----------------------------------------- > ==================================================== > This message contains PRIVILEGED and CONFIDENTIAL information that > is intended only for use by the named recipient. If you are not the > named recipient, any disclosure, dissemination, or action based on > the contents of this message is prohibited. In such case please > notify us and destroy and delete all copies of this transmission. > Thank you. > ==================================================== > -- Brett Porter Blog: http://blogs.exist.com/bporter/
