You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by "Brown, Carlton" <Ca...@compucredit.com> on 2008/02/28 22:31:24 UTC
Archiva selectively failing to proxy one particular artifact
I have a strange problem where an Archiva instance absolutely refuses to
retrieve one particular artifact from central under any circumstances...
it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've verified
that the instance can retrieve other artifacts, in fact maven-2.0.5.pom
retrieves just fine, as well as other randomly selected jars and pom
files. It's only maven-2.0.6.pom that it fails on. I also verified
that the file is in fact on maven central.
When I say I'm testing it, I mean that I'm pointing a browser to the
archiva URL designating an artifact that is not yet proxied, for example
http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/ma
ven-2.0.6.pom which returns a 404 error message.
Also, I don't know if this is related or not, but the 404 message
displays a munged, invalid URL:
The following resource does not exist:
http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom
<http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom>
Notice that the the context string "archiva" doesn't appear in the
displayed URL, and neither does the repository name "myrepo". But
since this behavior is reproducible with other well-formed URL's for
nonexistent artifacts, this may not be related to my problem at all.
Thanks in advance...
-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
RE : Archiva selectively failing to proxy one particular artifact
Posted by MATHUS Baptiste <ma...@mipih.fr>.
-------- Message d'origine--------
> De: Brett Porter [mailto:brett.porter@gmail.com]
> Date: sam. 01/03/2008 01:04
> À: archiva-users@maven.apache.org
> Objet : Re: Archiva selectively failing to proxy one particular artifact
>
> > 3) (Rhetorical question) WTF is up with Maven central having bad
> > checksums for Maven's own artifacts, and how can I be the first one to
> > notice this? Did I make some mistake, or is everyone except me ignoring
> > checksums?
In fact, you were not the first... See http://jira.codehaus.org/browse/MEV-530...
>
> Yeah, I remember 2.0.6 coming up - I'm not sure why it was never fixed.
>
Cheers.
-- Baptiste
Re: Archiva selectively failing to proxy one particular artifact
Posted by Brett Porter <br...@gmail.com>.
On 01/03/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> OK thanks, I figured out what's going on. The checksum was failing for
> http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.p
> om
>
> Testing confirms that it seems the checksums in the central repo are
> wrong. I manually ran md5 and sha1 sums on that file, and they do not
> match the sums stored in central. By comparison, the pom for 2.0.7 does
> not have this problem.
>
> Having confirmed this, if I could beg your indulgence for a couple of
> followup questions:
>
> 1) You said you didn't have this problem... I presume you have
> checksumming set to 'ignore' or 'fix' in Archiva?
right
> 2) Is a 404 really the only error we get on this problem? This is the
> same thing you'd get for a completely nonexistent artifact, it's kind of
> misleading.
we're looking to fix that for 1.0.2:
http://jira.codehaus.org/browse/MRM-159
> 3) (Rhetorical question) WTF is up with Maven central having bad
> checksums for Maven's own artifacts, and how can I be the first one to
> notice this? Did I make some mistake, or is everyone except me ignoring
> checksums?
Yeah, I remember 2.0.6 coming up - I'm not sure why it was never fixed.
- Brett
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
RE: Archiva selectively failing to proxy one particular artifact
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
OK thanks, I figured out what's going on. The checksum was failing for
http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.6/maven-2.0.6.p
om
Testing confirms that it seems the checksums in the central repo are
wrong. I manually ran md5 and sha1 sums on that file, and they do not
match the sums stored in central. By comparison, the pom for 2.0.7 does
not have this problem.
Having confirmed this, if I could beg your indulgence for a couple of
followup questions:
1) You said you didn't have this problem... I presume you have
checksumming set to 'ignore' or 'fix' in Archiva?
2) Is a 404 really the only error we get on this problem? This is the
same thing you'd get for a completely nonexistent artifact, it's kind of
misleading.
3) (Rhetorical question) WTF is up with Maven central having bad
checksums for Maven's own artifacts, and how can I be the first one to
notice this? Did I make some mistake, or is everyone except me ignoring
checksums?
-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com]
Sent: Friday, February 29, 2008 10:49 AM
To: archiva-users@maven.apache.org
Subject: Re: Archiva selectively failing to proxy one particular
artifact
the log configuration files are in
/apps/archiva/webapp/WEB-INF/classes/log4j.xml
On 01/03/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> How/where/what are the options to manipulate Archiva logging?
>
> It's on Windoze, probably not a permissions problem... I haven't done
> anything special to that particular directory, and there are scores of
> other artifacts being proxied and served without issue. Just one
day
> Maven started requesting the 2.0.6 pom for whatever reason, and
> Archiva refused to proxy that artifact (and only that artifact).
>
> Archiva also proxied successfully the Maven pom for 2.0.5 or 2.0.7
> (which was requested by Maven 2.0.8 for reasons known only to itself,
> which I'll need to investigate later).
>
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
>
> Sent: Thursday, February 28, 2008 5:16 PM
> To: archiva-users@maven.apache.org
> Subject: Re: Archiva selectively failing to proxy one particular
> artifact
>
> what about permissions problems? anything in the logs (may need to
> turn up the level a bit)?
>
> The other thought is whether the database has something in it that
> causes it not to work, but I don't think it's consulted first.
>
> I'm out of other ideas... really quite strange.
>
> - Brett
>
> On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> > It populates just an empty 2.0.6 directory. The behavior is the
> same
>
> > whether that dir is pre-existing or not. I guess I could try >
> installing that artifact by hand and see what happens.
> >
> > I've also tried restarting tomcat as well. I'm not sure how I
> might > go about restoring the state other than that.
> >
> >
> > -----Original Message-----
> > From: Brett Porter [mailto:brett.porter@gmail.com] > Sent:
> Thursday, February 28, 2008 4:45 PM > To:
> archiva-users@maven.apache.org > Subject: Re: Archiva selectively
> failing to proxy one particular > artifact > > it works for me, so
> there must be a state problem rather than a bug > in the proxying
> related to that artifact.
> >
> > Do you have any content for that version in the managed
repository?
> >
> > - Brett
> >
> > On 29/02/2008, Brown, Carlton <Ca...@compucredit.com>
wrote:
> > > I have a strange problem where an Archiva instance absolutely >
> refuses > to retrieve one particular artifact from central under any
>
> > circumstances...
> > > it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've
> verified
> > > that the instance can retrieve other artifacts, in fact > >
> maven-2.0.5.pom retrieves just fine, as well as other randomly >
> selected jars and pom
> > > files. It's only maven-2.0.6.pom that it fails on. I also
> verified
> > > that the file is in fact on maven central.
> > >
> > > When I say I'm testing it, I mean that I'm pointing a browser
> to > the > > > archiva URL designating an artifact that is not yet
> proxied, for >
>
> > example >
> >
> http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/
> > > ma ven-2.0.6.pom which returns a 404 error message.
> > >
> > > Also, I don't know if this is related or not, but the 404
> message
>
> > > displays a munged, invalid URL:
> > > The following resource does not exist:
> > >
> > >
> >
> http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom
> > >
> > >
> >
> <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.po
> > > m>
> > >
> > >
> > > Notice that the the context string "archiva" doesn't appear in
> the > > displayed URL, and neither does the repository name
"myrepo".
> But
> > > since this behavior is reproducible with other well-formed
> URL's > for > > > nonexistent artifacts, this may not be related
> to my problem at all.
> > >
> > > Thanks in advance...
> > >
> > >
> > >
> > >
> > > -----------------------------------------
> > > ====================================================
> > > This message contains PRIVILEGED and CONFIDENTIAL information
> > that > is intended only for use by the named recipient. If you are
> > not the > named recipient, any disclosure, dissemination, or
> action > based on > the contents of this message is prohibited. In
> such case > please > notify us and destroy and delete all copies
> of this transmission.
> > > Thank you.
> > > ====================================================
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/ >
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> -----------------------------------------
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL information that
> is intended only for use by the named recipient. If you are not the
> named recipient, any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such case please
> notify us and destroy and delete all copies of this transmission.
> Thank you.
> ====================================================
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Archiva selectively failing to proxy one particular artifact
Posted by Brett Porter <br...@gmail.com>.
the log configuration files are in
/apps/archiva/webapp/WEB-INF/classes/log4j.xml
On 01/03/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> How/where/what are the options to manipulate Archiva logging?
>
> It's on Windoze, probably not a permissions problem... I haven't done
> anything special to that particular directory, and there are scores of
> other artifacts being proxied and served without issue. Just one day
> Maven started requesting the 2.0.6 pom for whatever reason, and Archiva
> refused to proxy that artifact (and only that artifact).
>
> Archiva also proxied successfully the Maven pom for 2.0.5 or 2.0.7
> (which was requested by Maven 2.0.8 for reasons known only to itself,
> which I'll need to investigate later).
>
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
>
> Sent: Thursday, February 28, 2008 5:16 PM
> To: archiva-users@maven.apache.org
> Subject: Re: Archiva selectively failing to proxy one particular
> artifact
>
> what about permissions problems? anything in the logs (may need to turn
> up the level a bit)?
>
> The other thought is whether the database has something in it that
> causes it not to work, but I don't think it's consulted first.
>
> I'm out of other ideas... really quite strange.
>
> - Brett
>
> On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> > It populates just an empty 2.0.6 directory. The behavior is the same
>
> > whether that dir is pre-existing or not. I guess I could try
> > installing that artifact by hand and see what happens.
> >
> > I've also tried restarting tomcat as well. I'm not sure how I might
> > go about restoring the state other than that.
> >
> >
> > -----Original Message-----
> > From: Brett Porter [mailto:brett.porter@gmail.com]
> > Sent: Thursday, February 28, 2008 4:45 PM
> > To: archiva-users@maven.apache.org
> > Subject: Re: Archiva selectively failing to proxy one particular
> > artifact
> >
> > it works for me, so there must be a state problem rather than a bug
> > in the proxying related to that artifact.
> >
> > Do you have any content for that version in the managed repository?
> >
> > - Brett
> >
> > On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> > > I have a strange problem where an Archiva instance absolutely
> > refuses > to retrieve one particular artifact from central under any
>
> > circumstances...
> > > it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've
> verified
> > > that the instance can retrieve other artifacts, in fact >
> > maven-2.0.5.pom retrieves just fine, as well as other randomly
> > selected jars and pom
> > > files. It's only maven-2.0.6.pom that it fails on. I also
> verified
> > > that the file is in fact on maven central.
> > >
> > > When I say I'm testing it, I mean that I'm pointing a browser to
> > the
> >
> > > archiva URL designating an artifact that is not yet proxied, for >
>
> > example >
> > http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/
> > > ma ven-2.0.6.pom which returns a 404 error message.
> > >
> > > Also, I don't know if this is related or not, but the 404 message
>
> > > displays a munged, invalid URL:
> > > The following resource does not exist:
> > >
> > >
> > http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom
> > >
> > >
> > <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.po
> > > m>
> > >
> > >
> > > Notice that the the context string "archiva" doesn't appear in the
> > > displayed URL, and neither does the repository name "myrepo".
> But
> > > since this behavior is reproducible with other well-formed URL's
> > for
> >
> > > nonexistent artifacts, this may not be related to my problem at
> all.
> > >
> > > Thanks in advance...
> > >
> > >
> > >
> > >
> > > -----------------------------------------
> > > ====================================================
> > > This message contains PRIVILEGED and CONFIDENTIAL information
> > that > is intended only for use by the named recipient. If you are
> > not the > named recipient, any disclosure, dissemination, or action
> > based on > the contents of this message is prohibited. In such case
> > please > notify us and destroy and delete all copies of this
> transmission.
> > > Thank you.
> > > ====================================================
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> -----------------------------------------
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL
> information that is intended only for use by the
> named recipient. If you are not the named recipient,
> any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such
> case please notify us and destroy and delete all
> copies of this transmission. Thank you.
> ====================================================
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
RE: Archiva selectively failing to proxy one particular artifact
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
How/where/what are the options to manipulate Archiva logging?
It's on Windoze, probably not a permissions problem... I haven't done
anything special to that particular directory, and there are scores of
other artifacts being proxied and served without issue. Just one day
Maven started requesting the 2.0.6 pom for whatever reason, and Archiva
refused to proxy that artifact (and only that artifact).
Archiva also proxied successfully the Maven pom for 2.0.5 or 2.0.7
(which was requested by Maven 2.0.8 for reasons known only to itself,
which I'll need to investigate later).
-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com]
Sent: Thursday, February 28, 2008 5:16 PM
To: archiva-users@maven.apache.org
Subject: Re: Archiva selectively failing to proxy one particular
artifact
what about permissions problems? anything in the logs (may need to turn
up the level a bit)?
The other thought is whether the database has something in it that
causes it not to work, but I don't think it's consulted first.
I'm out of other ideas... really quite strange.
- Brett
On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> It populates just an empty 2.0.6 directory. The behavior is the same
> whether that dir is pre-existing or not. I guess I could try
> installing that artifact by hand and see what happens.
>
> I've also tried restarting tomcat as well. I'm not sure how I might
> go about restoring the state other than that.
>
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Thursday, February 28, 2008 4:45 PM
> To: archiva-users@maven.apache.org
> Subject: Re: Archiva selectively failing to proxy one particular
> artifact
>
> it works for me, so there must be a state problem rather than a bug
> in the proxying related to that artifact.
>
> Do you have any content for that version in the managed repository?
>
> - Brett
>
> On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> > I have a strange problem where an Archiva instance absolutely
> refuses > to retrieve one particular artifact from central under any
> circumstances...
> > it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've
verified
> > that the instance can retrieve other artifacts, in fact >
> maven-2.0.5.pom retrieves just fine, as well as other randomly
> selected jars and pom
> > files. It's only maven-2.0.6.pom that it fails on. I also
verified
> > that the file is in fact on maven central.
> >
> > When I say I'm testing it, I mean that I'm pointing a browser to
> the
>
> > archiva URL designating an artifact that is not yet proxied, for >
> example >
> http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/
> > ma ven-2.0.6.pom which returns a 404 error message.
> >
> > Also, I don't know if this is related or not, but the 404 message
> > displays a munged, invalid URL:
> > The following resource does not exist:
> >
> >
> http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom
> >
> >
> <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.po
> > m>
> >
> >
> > Notice that the the context string "archiva" doesn't appear in the
> > displayed URL, and neither does the repository name "myrepo".
But
> > since this behavior is reproducible with other well-formed URL's
> for
>
> > nonexistent artifacts, this may not be related to my problem at
all.
> >
> > Thanks in advance...
> >
> >
> >
> >
> > -----------------------------------------
> > ====================================================
> > This message contains PRIVILEGED and CONFIDENTIAL information
> that > is intended only for use by the named recipient. If you are
> not the > named recipient, any disclosure, dissemination, or action
> based on > the contents of this message is prohibited. In such case
> please > notify us and destroy and delete all copies of this
transmission.
> > Thank you.
> > ====================================================
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
-----------------------------------------
====================================================
This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on
the contents of this message is prohibited. In such
case please notify us and destroy and delete all
copies of this transmission. Thank you.
====================================================
Re: Archiva selectively failing to proxy one particular artifact
Posted by Brett Porter <br...@gmail.com>.
what about permissions problems? anything in the logs (may need to
turn up the level a bit)?
The other thought is whether the database has something in it that
causes it not to work, but I don't think it's consulted first.
I'm out of other ideas... really quite strange.
- Brett
On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> It populates just an empty 2.0.6 directory. The behavior is the same
> whether that dir is pre-existing or not. I guess I could try installing
> that artifact by hand and see what happens.
>
> I've also tried restarting tomcat as well. I'm not sure how I might go
> about restoring the state other than that.
>
>
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Thursday, February 28, 2008 4:45 PM
> To: archiva-users@maven.apache.org
> Subject: Re: Archiva selectively failing to proxy one particular
> artifact
>
> it works for me, so there must be a state problem rather than a bug in
> the proxying related to that artifact.
>
> Do you have any content for that version in the managed repository?
>
> - Brett
>
> On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> > I have a strange problem where an Archiva instance absolutely refuses
> > to retrieve one particular artifact from central under any
> circumstances...
> > it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've verified
> > that the instance can retrieve other artifacts, in fact
> > maven-2.0.5.pom retrieves just fine, as well as other randomly
> selected jars and pom
> > files. It's only maven-2.0.6.pom that it fails on. I also verified
> > that the file is in fact on maven central.
> >
> > When I say I'm testing it, I mean that I'm pointing a browser to the
>
> > archiva URL designating an artifact that is not yet proxied, for
> > example
> > http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/
> > ma ven-2.0.6.pom which returns a 404 error message.
> >
> > Also, I don't know if this is related or not, but the 404 message
> > displays a munged, invalid URL:
> > The following resource does not exist:
> >
> > http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom
> >
> > <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.po
> > m>
> >
> >
> > Notice that the the context string "archiva" doesn't appear in the
> > displayed URL, and neither does the repository name "myrepo". But
> > since this behavior is reproducible with other well-formed URL's for
>
> > nonexistent artifacts, this may not be related to my problem at all.
> >
> > Thanks in advance...
> >
> >
> >
> >
> > -----------------------------------------
> > ====================================================
> > This message contains PRIVILEGED and CONFIDENTIAL information that
> > is intended only for use by the named recipient. If you are not the
> > named recipient, any disclosure, dissemination, or action based on
> > the contents of this message is prohibited. In such case please
> > notify us and destroy and delete all copies of this transmission.
> > Thank you.
> > ====================================================
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
RE: Archiva selectively failing to proxy one particular artifact
Posted by "Brown, Carlton" <Ca...@compucredit.com>.
It populates just an empty 2.0.6 directory. The behavior is the same
whether that dir is pre-existing or not. I guess I could try installing
that artifact by hand and see what happens.
I've also tried restarting tomcat as well. I'm not sure how I might go
about restoring the state other than that.
-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com]
Sent: Thursday, February 28, 2008 4:45 PM
To: archiva-users@maven.apache.org
Subject: Re: Archiva selectively failing to proxy one particular
artifact
it works for me, so there must be a state problem rather than a bug in
the proxying related to that artifact.
Do you have any content for that version in the managed repository?
- Brett
On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> I have a strange problem where an Archiva instance absolutely refuses
> to retrieve one particular artifact from central under any
circumstances...
> it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've verified
> that the instance can retrieve other artifacts, in fact
> maven-2.0.5.pom retrieves just fine, as well as other randomly
selected jars and pom
> files. It's only maven-2.0.6.pom that it fails on. I also verified
> that the file is in fact on maven central.
>
> When I say I'm testing it, I mean that I'm pointing a browser to the
> archiva URL designating an artifact that is not yet proxied, for
> example
> http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/
> ma ven-2.0.6.pom which returns a 404 error message.
>
> Also, I don't know if this is related or not, but the 404 message
> displays a munged, invalid URL:
> The following resource does not exist:
>
> http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom
>
> <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.po
> m>
>
>
> Notice that the the context string "archiva" doesn't appear in the
> displayed URL, and neither does the repository name "myrepo". But
> since this behavior is reproducible with other well-formed URL's for
> nonexistent artifacts, this may not be related to my problem at all.
>
> Thanks in advance...
>
>
>
>
> -----------------------------------------
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL information that
> is intended only for use by the named recipient. If you are not the
> named recipient, any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such case please
> notify us and destroy and delete all copies of this transmission.
> Thank you.
> ====================================================
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Archiva selectively failing to proxy one particular artifact
Posted by Brett Porter <br...@gmail.com>.
it works for me, so there must be a state problem rather than a bug in
the proxying related to that artifact.
Do you have any content for that version in the managed repository?
- Brett
On 29/02/2008, Brown, Carlton <Ca...@compucredit.com> wrote:
> I have a strange problem where an Archiva instance absolutely refuses to
> retrieve one particular artifact from central under any circumstances...
> it is /org/apache/maven/maven/2.0.6/maven-2.0.6.pom . I've verified
> that the instance can retrieve other artifacts, in fact maven-2.0.5.pom
> retrieves just fine, as well as other randomly selected jars and pom
> files. It's only maven-2.0.6.pom that it fails on. I also verified
> that the file is in fact on maven central.
>
> When I say I'm testing it, I mean that I'm pointing a browser to the
> archiva URL designating an artifact that is not yet proxied, for example
> http://myarchivahost/archiva/repository/myrepo/org/apache/maven/2.0.6/ma
> ven-2.0.6.pom which returns a 404 error message.
>
> Also, I don't know if this is related or not, but the 404 message
> displays a munged, invalid URL:
> The following resource does not exist:
> http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom
> <http://myarchivahost/repository/org/apache/maven/2.0.6/maven-2.0.6.pom>
>
>
> Notice that the the context string "archiva" doesn't appear in the
> displayed URL, and neither does the repository name "myrepo". But
> since this behavior is reproducible with other well-formed URL's for
> nonexistent artifacts, this may not be related to my problem at all.
>
> Thanks in advance...
>
>
>
>
> -----------------------------------------
> ====================================================
> This message contains PRIVILEGED and CONFIDENTIAL
> information that is intended only for use by the
> named recipient. If you are not the named recipient,
> any disclosure, dissemination, or action based on
> the contents of this message is prohibited. In such
> case please notify us and destroy and delete all
> copies of this transmission. Thank you.
> ====================================================
--
Brett Porter
Blog: http://blogs.exist.com/bporter/