Mailing-List: contact repo-maintainers-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: repo-maintainers@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of brianf@reply.infinity.nu
 designates 205.210.42.66 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9516C.47DE23B6"
Subject: RE: [Artifactory-users] Artifactory 1.3 has been DOS'ing
 theCentralrepository
Date: Fri, 28 Nov 2008 10:16:25 -0500
Message-ID: <2BABBE7D2A66E04DB8A66A527D29927E404B17@intrepid.infinity.nu>
In-Reply-To: <2BABBE7D2A66E04DB8A66A527D29927E404B16@intrepid.infinity.nu>
Thread-Topic: [Artifactory-users] Artifactory 1.3 has been DOS'ing
 theCentralrepository
Thread-Index: AclRZ6ALdXi3YNX0QmWJnTy4/rFv2AAA0VwAAABOIlA=
References: 
 <2BABBE7D2A66E04DB8A66A527D29927E404B15@intrepid.infinity.nu><036389E4-867F-44D6-BE53-774C220B15C4@yahoo.de>
 <2BABBE7D2A66E04DB8A66A527D29927E404B16@intrepid.infinity.nu>
From: "Brian E. Fox" <brianf@reply.infinity.nu>
To: <artifactory-users@lists.sourceforge.net>
Cc: <repo-maintainers@maven.apache.org>,
	"Maven Users List" <users@maven.apache.org>

------_=_NextPart_001_01C9516C.47DE23B6
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Robert, just realized I missed one of your questions: The block went
into effect early this morning. Any trouble you had last week was likely
due to the connection being saturated by the index downloads.

=20

From: Brian E. Fox [mailto:brianf@reply.infinity.nu]=20
Sent: Friday, November 28, 2008 10:08 AM
To: artifactory-users@lists.sourceforge.net
Cc: repo-maintainers@maven.apache.org; Maven Users List; Maven Project
Management Committee List
Subject: Re: [Artifactory-users] Artifactory 1.3 has been DOS'ing
theCentralrepository

=20

Hi Robert,

Artifactory doesn't use a unique user-agent, which further compounded
the trouble finding this problem. I can't confirm which versions of
Artifactory have this issue and even if we could, they all appear to be
using the exact same user-agent so there's not much we could do to
separate it out.

=20

--Brian

=20

From: Robert Oschwald [mailto:robertoschwald@yahoo.de]=20
Sent: Friday, November 28, 2008 9:42 AM
To: artifactory-users@lists.sourceforge.net
Cc: repo-maintainers@maven.apache.org; Maven Users List; Maven Project
Management Committee List
Subject: Re: [Artifactory-users] Artifactory 1.3 has been DOS'ing
theCentral repository

=20

Brian,

=20

thanks for the info.

We recognized several problems accessing the repo using Artifactory last
week. We are on Version 1.2.5u1, which is not affected, right?

We figured out that the connection problems were only seen on some http
clients, like wget, but not with others like ff,ie,lynx.

=20

So my question is: Have you blocked access for all artifactory versions
last week or was it just due to the performance problems? If you blocked
access to all artifactory versions (I think on the agent field), could
you distinguish between "good" and "bad" versions?

=20

Robert

=20

	To protect the Maven Community from ongoing troubles, we have
had to take the extra-ordinary step of blocking all downloads of the
index file by Artifactory until this is resolved. Upon doing this, the
traffic has fallen to 10% of what it has been in the recent past. If you
are using Artifactory, please adjust this cron definition to run only
weekly and save yourself and us tons of wasted bandwidth and money.


------_=_NextPart_001_01C9516C.47DE23B6--