From users-return-1757-apmail-archiva-users-archive=archiva.apache.org@archiva.apache.org Wed Aug 20 13:29:13 2008 Return-Path: Delivered-To: apmail-archiva-users-archive@www.apache.org Received: (qmail 66828 invoked from network); 20 Aug 2008 13:29:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Aug 2008 13:29:06 -0000 Received: (qmail 87831 invoked by uid 500); 20 Aug 2008 13:29:00 -0000 Delivered-To: apmail-archiva-users-archive@archiva.apache.org Received: (qmail 87782 invoked by uid 500); 20 Aug 2008 13:29:00 -0000 Mailing-List: contact users-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@archiva.apache.org Delivered-To: mailing list users@archiva.apache.org Received: (qmail 87738 invoked by uid 500); 20 Aug 2008 13:29:00 -0000 Delivered-To: apmail-maven-archiva-users@maven.apache.org Received: (qmail 87724 invoked by uid 99); 20 Aug 2008 13:29:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2008 06:29:00 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of keepitsimple12@gmail.com designates 209.85.198.244 as permitted sender) Received: from [209.85.198.244] (HELO rv-out-0708.google.com) (209.85.198.244) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2008 13:28:04 +0000 Received: by rv-out-0708.google.com with SMTP id b17so378241rvf.36 for ; Wed, 20 Aug 2008 06:28:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=L8sBfEgN6jVtNyVz+HJQ1KjXvKqmQ/0KBR1HkbVT/FY=; b=xvxKJ1JuwGNTJygC0ac5bzLA8Ipr4pzq7ZFcdhDnXNOJd2PeZc3zSu6wZ1Vl6ggzo9 DI4DCT+CDyj42aCDLUo0r6cFig4U/hM6o1WmwMPlFEENH2qzYE41x32x2l0mVj/97wY4 sn2kx52yeMlAPH3uUZyv+k3uobKt17hCP79is= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=W5v6PuxJuCohf2i6rv6TJMT7qNtKy9EGbjKU2fsBwu8M9aUyUHMSUVjtMJJdqNHCyS uAUpVxR4EcBKDr4B5lxbi3PHE7CaXNIbadtByq8AzEAWnjvjJ4p4vwV6hDhkeU9eNedK 5DUXJXwDP9nt1DrurEe61o3tNpdjcev1OzkZo= Received: by 10.141.133.14 with SMTP id k14mr33121rvn.127.1219238904437; Wed, 20 Aug 2008 06:28:24 -0700 (PDT) Received: by 10.140.186.9 with HTTP; Wed, 20 Aug 2008 06:28:24 -0700 (PDT) Message-ID: Date: Wed, 20 Aug 2008 09:28:24 -0400 From: "Zemian Deng" To: archiva-users@maven.apache.org Subject: daisy chain archiva webapp proxies doesn't seem to work MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11783_7261635.1219238904427" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_11783_7261635.1219238904427 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I have to archiva instance running on separated hosts A and B. I have added a remote repo of archiveB into archivaA, and for most of the time they works great. But sometimes when i do a release to archivaB, the archivaA will not pull down the artifact. Is there reason for this? I can verify that archivaB does indeed worked becuase i have a project build sucessful with the latest dependencies on the artifact x, but when I switch to archivaA, it will failed that it can't find the artifact. So my question is, is there time period that archiva will wait before it check remote repo, even when you have a project requesting a artifact that's missing from it? If so, is there way I can force it to pull that down into archiva? Thanks, -Z -- Sweet - a Scala web framework: http://code.google.com/p/sweetscala ------=_Part_11783_7261635.1219238904427--