Archiva 1.3.5 does not build the maven-metadata file automatically this could be an issue with the speed, since it needs to then scan the repository instead of being directed. Fixed in 1.4 though See bug http://jira.codehaus.org/browse/MRM-1477
Nz On Thu, Jul 14, 2011 at 11:08 PM, Brett Porter <[email protected]> wrote: > > On 14/07/2011, at 12:50 AM, Cristiano Costantini wrote: > > > any "Proxy Connector" is set with: > > > > Return error when: always > > Cache failures: yes > > Releases: once > > On remote error: stop > > Checksum: fix > > Snapshots: never > > > > (I want stable builds, I want only release artifacts! ;-) ) > > This looks right > > > > > Two Important things I've noticed: all the request done by archiva lead > to > > 404 Bad Request responses (then, archiva returns a cached artifact to the > > maven process) and if a disable all the proxy connectors, then yes the > build > > is fast! > > 400 remotely, or Archiva is giving back 400? (I assume you meant 400 Bad > Request, not 404 Not Found) > > > > > Anyone can help me on configuring Archiva to do not repeat any type of > > request to remote servers (for releases) at all? > > Could you point me out on which relevant configuration parameter I can > send > > you to investigate if I'm doing something wrong? > > > > I'm using archiva 1.3.5. > > It should never repeat for an artifact - but it will for maven-metadata.xml > files when requested by the client. There's two things you can do to speed > it up: > - add whitelists on the proxy connectors where you know only a subset of > artifacts should come from there - that way it won't ever look out there > unless you intended it to > - make sure the maven instance has similar <repository> definitions so it > doesn't harrass Archiva for snapshots it is never going to have > > The other thing to check is the network speed from Archiva to the world - > though I'm also curious about the error you listed above. > > HTH, > Brett > > -- > Brett Porter > [email protected] > http://brettporter.wordpress.com/ > http://au.linkedin.com/in/brettporter > > > > >
