Return-Path: 
 <ivy-user-return-4970-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 29830 invoked from network); 19 Mar 2009 17:18:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 19 Mar 2009 17:18:29 -0000
Received: (qmail 28069 invoked by uid 500); 19 Mar 2009 17:18:27 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 28052 invoked by uid 500); 19 Mar 2009 17:18:27 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 28041 invoked by uid 99); 19 Mar 2009 17:18:27 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2009 10:18:27 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of sberlin@gmail.com designates
 74.125.44.157 as permitted sender)
Received: from [74.125.44.157] (HELO yx-out-1718.google.com) (74.125.44.157)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2009 17:18:20 +0000
Received: by yx-out-1718.google.com with SMTP id 34so448803yxf.70
        for <ivy-user@ant.apache.org>; Thu, 19 Mar 2009 10:17:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=Mbz8qHcr8tAjTRlUHMI75SM5KJhZvtAaQBFO32AoeCE=;
        b=E66+hafkyHiushRa8SFWkvqXjd2bGRw9aRK97yuCcMGxv0ZAVDbxC6HrPn0JYdvCdZ
         3DDkd2V2NV9JdtzHHngX93EfqnoiN5XGJlpgLwXLnN0wskjim2wG8I5y7S1PmCMhPi9E
         kpEpvupYtqhuRzrTK3lzvfIpnNuUHJNOBhpHw=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=mjjOyhnGo+o8GW0YmCio4BwaNSO4Kz8hD5G52/Wc3x2HCTQXDQBWBMGwIL85FZGiJ+
         I1G9BvjSuyZMRwN0Dul/V8kd12NZaKXxVxKhl7L1knIq2EM/WoTtrJXU2cHIDqnNGOlD
         AJ1vhPwa2osEEZltdAbSD6OIKrbT3YV7uk/gs=
MIME-Version: 1.0
Received: by 10.220.99.149 with SMTP id u21mr1401648vcn.94.1237483078955;
 Thu,
	19 Mar 2009 10:17:58 -0700 (PDT)
In-Reply-To: <19196d860903190933v4bb19c82h816bc14161e161b5@mail.gmail.com>
References: <-3093075934296175793@unknownmsgid>
	 <19196d860903190933v4bb19c82h816bc14161e161b5@mail.gmail.com>
Date: Thu, 19 Mar 2009 13:17:58 -0400
Message-ID: <19196d860903191017l736e1a74i605d2f28b304f6b0@mail.gmail.com>
Subject: Re: Running Ivy in parallel builds
From: Sam Berlin <sberlin@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: text/plain; charset=ISO-8859-13
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

I'm updating the <caches> element of the ivy-settings, but am
encountering what looks to be a strange bug.

If I set:

	<caches
	        repositoryCacheDir=3D"${ivy.default.ivy.user.dir}/repositoryCache"
	        resolutionCacheDir=3D"${project.home}/.ivy2/resolutionCache"
	        lockStrategy=3D"artifact-lock"
	        useOrigin=3D"true"/>

Then it appears that the repositoryCacheDir is ignored, however, if I set:

	<caches defaultCacheDir=3D"${ivy.default.ivy.user.dir}/defaultCache"
	        repositoryCacheDir=3D"${ivy.default.ivy.user.dir}/repositoryCache"
	        resolutionCacheDir=3D"${project.home}/.ivy2/resolutionCache"
	        lockStrategy=3D"artifact-lock"
	        useOrigin=3D"true"/>
	=09
then it appears that the repositoryCacheDir is correctly used (and the
defaultCacheDir is properly ignored).

Sam
	=09

2009/3/19 Sam Berlin <sberlin@gmail.com>:
> Yes, I have noticed significant problems when using ivy in a parallel
> build environment (essentially, any build-server), and we've only had
> Ivy in use on the buildserver for ~12 hours. =A0The only solution I can
> think of is to make the cache local per build, which is pretty far
> from ideal.
>
> Any suggestions for how to make Ivy more robust against concurrent builds=
?
>
> Sam
>
> 2009/3/19 Uldis Karlovs-Karlovskis <uldis.karlovs-karlovskis@ctco.lv>:
>> And this is not all. Previous case was when artifact is already in cache=
. If
>> Ivy needs to download new artifact then parallel execution gives somethi=
ng
>> like this:
>>
>> ---------------------------------------------------------------------
>> =A0 =A0 =A0 =A0| | modules || artifacts |
>> =A0 =A0 =A0 =A0| conf | number| search|dwnlded|evicted|| number|dwnlded|
>>
>> ---------------------------------------------------------------------
>> =A0 =A0 =A0 =A0| default | 4 | 0 | 0 | 0 || 6 | 0 |
>>
>> ---------------------------------------------------------------------
>>
>> =A0:: problems summary ::
>> =A0:::: WARNINGS
>> =A0 =A0 =A0 =A0problem while downloading module descriptor:
>> http://server/download?name=3Dsomemodule&version=3D1.3.1.16&file=3Dsomem=
odule&file
>> Type=3Dxml: impossible to move part file to definitive one:
>> /root/.ivy2/cache/ctco/somemodule/ivy-1.3.1.16.xml.original.part ->
>> /root/.ivy2/cache/ctco/somemodule/ivy-1.3.1.16.xml.original (21ms)
>>
>> =A0 =A0 =A0 =A0 module not found: ctco#somemodule;1.3.1.16
>>
>> =A0 =A0 =A0 =A0=3D=3D=3D=3D bones-repository: tried
>>
>>
>> http://server/download?name=3Dsomemodule&version=3D1.3.1.16&file=3Dsomem=
odule&file
>> Type=3Dxml
>>
>> =A0 =A0 =A0 =A0 ::::::::::::::::::::::::::::::::::::::::::::::
>>
>> =A0 =A0 =A0 =A0 :: UNRESOLVED DEPENDENCIES ::
>>
>> =A0 =A0 =A0 =A0 ::::::::::::::::::::::::::::::::::::::::::::::
>>
>> =A0 =A0 =A0 =A0 :: ctco#somemodule;1.3.1.16: not found
>>
>> =A0 =A0 =A0 =A0 ::::::::::::::::::::::::::::::::::::::::::::::
>>
>>
>>
>> =A0:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
>> =A0command exit code: 1
>>
>> Regards,
>> Uldis, C. T. Co
>> uldis.karlovs-karlovskis@ctco.lv
>>
>>
>> -----Original Message-----
>> From: Uldis Karlovs-Karlovskis [mailto:uldis.karlovs-karlovskis@ctco.lv]
>> Sent: ceturtdiena, 2009. gada 19. mart=E2 17:37
>> To: ivy-user@ant.apache.org
>> Subject: Running Ivy in parallel builds
>>
>> Hello!
>>
>>
>>
>> Have You tested running Ivy in more than one build at the time?
>>
>> I see there are few files in cache which got updated every time I run Iv=
y.
>> When my build system is running more than one process at the time someti=
mes
>> I got this exception:
>>
>> :: retrieving :: lv.ctco#scm-bootstrap
>>
>> =A0confs: [default]
>>
>> =A0Caught: java.lang.RuntimeException: problem during retrieve of
>> <namespace>#<module>: java.text.ParseException: failed to parse report:
>> /root/.ivy2/cache/lv.ctco-scm-bootstrap-default.xml: Premature end of fi=
le.
>>
>> =A0command exit code: 1
>>
>>
>>
>>
>>
>> Uldis Karlovs - Karlovskis
>>
>> Lead SCM Engineer
>>
>> System Configuration Management
>>
>> C.T.Co
>>
>> Mobile: +371 29 345 210
>>
>>
>>
>>
>>
>