Multi-threaded artifact resolver corrupts artifacts on download
---------------------------------------------------------------
Key: MNG-4742
URL: http://jira.codehaus.org/browse/MNG-4742
Project: Maven 2 & 3
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.2.1
Environment: Windows XP, JDK 1.6, Maven 2.2.1
Reporter: Cornel Masson
It seems that the artifact resolver is _not thread-safe_, resulting in
corruption of artifacts as they are downloaded.
We have a large build and were seeing numerous CHECKSUM failures, even on Maven
jars from Central. On closer inspection, the downloaded JARs themselves
appeared corrupted, i.e. it wasn't just corrupt checksums. The other funny
thing was that, for each build, it happened on random, _different_ JARs. This
happened on JARs from any repository (public, or our own Nexus repo), so it had
nothing to do with possible corruptions of our own jars on deploy.
We first tried all the suggestions on the Net, including setting the wagon
provider to httpclient. Nothing worked. Then we found the answer:
*-Dmaven.artifact.threads=1*
As soon as you restrict the artifact resolver to a single thread, the problem
goes away (apparently the Maven default is to use up to 5 threads). This looks
like a thread-safety issue, with threads perhaps overwriting each other's
streams.
What I don't understand is that this bug hasn't surfaced earlier, since we have
a standard Maven installation. Note that it happens even when *not* using
Nexus, i.e. when going directly to public repositories.
--
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
