You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Brett Porter <br...@apache.org> on 2007/01/27 23:47:28 UTC
Re: proxying was: two 500 errors
Joakim,
Was this something that was changed?
- Brett
On 28/01/2007, at 9:37 AM, Wendy Smoak wrote:
> On 1/27/07, Brett Porter <br...@apache.org> wrote:
>
>> The instructions are incorrect - you acccess via the /repository/
>> URL, which can be configured inside Archiva to proxy an external
>> repository. Where did you see these instructions?
>
> http://docs.codehaus.org/display/MAVENUSER/Archiva+as+a+Proxy
>
> IME, unless you use the /proxy url, Archiva will not actually proxy
> the requests. Could be that's fixed now, this was a while ago.
>
> --
> Wendy
Re: proxying was: two 500 errors
Posted by drekka <de...@aegeon.com.au>.
Hi all,
I've just found this thread as a result of checking through the wiki page I
wrote on getting started with Archiva.
Thanks to Wendy for added a quick comment or I would have not know there was
an issue.
I think this whole episode just highlights the problems with not having
proper releases. Here the users are at the mercy of the developers. Should
something get changed or worse, broken, then it's the users who suffer, not
just the developers. Plus it makes it far more difficult for documentation
authors to update wiki content because they cannot mark changes against
versions and thus have to put comments in like "if your software is older
than ..." and "try this or this or this ..." etc.
I think it's time archiva was given proper releases with version numbers and
change logs. It's time binary releases are put on the web site so users who
just want to use it can download, setup and be assured of the functionality
they are getting. So that next time someone makes a mistake or changes
something without realising the implications, ordinary users don't get
burned.
I"m sorry if this sounds like a rant, but I seriously disagree with
development source code being presented to users as the only way to access
and use software.
ciao
Derek
brettporter wrote:
>
> Joakim,
>
> Was this something that was changed?
>
> - Brett
>
> On 28/01/2007, at 9:37 AM, Wendy Smoak wrote:
>
>> On 1/27/07, Brett Porter <br...@apache.org> wrote:
>>
>>> The instructions are incorrect - you acccess via the /repository/
>>> URL, which can be configured inside Archiva to proxy an external
>>> repository. Where did you see these instructions?
>>
>> http://docs.codehaus.org/display/MAVENUSER/Archiva+as+a+Proxy
>>
>> IME, unless you use the /proxy url, Archiva will not actually proxy
>> the requests. Could be that's fixed now, this was a while ago.
>>
>> --
>> Wendy
>
>
--
View this message in context: http://www.nabble.com/Re%3A-proxying-was%3A-two-500-errors-tf3129411.html#a8840179
Sent from the archiva-dev mailing list archive at Nabble.com.
Re: proxying was: two 500 errors
Posted by Andrew Williams <an...@handyande.co.uk>.
looks to me like webdav versions conflicting, but that is just a
glancing look as I am at work.
Can give it a closer probe tonight.
A
Brett Porter wrote:
> This seems to be the same problem that a couple of other users have
> reported for /repository. I'm CCing Andy in case he recognises it (not
> sure if he is on this list?).
>
> - Brett
>
> On 29/01/2007, at 4:46 AM, Wendy Smoak wrote:
>
>> On 1/28/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
>>> Those wiki docs are now incorrect.
>>> The /proxy/ URL was removed as it didn't support security or webdav or
>>> the ability to upload content on.
>>> Having 2 URLs to access the repository was confusing.
>>>
>>> I'll update the wiki (and the archiva-site docs) to reflect the current
>>> usage.
>>
>> Okay, with r500200, the /proxy url no longer works. (There is no
>> Action mapped for namespace / and action name proxy.)
>>
>> However, proxying also does not work with the the /repository URL.
>>
>> I have central proxied through 'myrepo', and the guest user is a
>> repository observer.
>>
>> 1. rm -rf $M2_REPO/junit
>> 2. override 'central' with url
>> http://localhost:9091/archiva/repository/myrepo/
>> 2. quickstart archetype ... mvn install
>>
>> The build fails due to the missing JUnit dependency, and the Archiva
>> logs show:
>>
>> INFO | jvm 1 | 2007/01/28 10:34:01 | WARNING:
>> /archiva/repository/myrepo/ju
>> nit/junit/3.8.1/junit-3.8.1.jar:
>> INFO | jvm 1 | 2007/01/28 10:34:01 |
>> org.codehaus.plexus.component.reposito
>> ry.exception.ComponentLookupException: Component descriptor cannot be
>> found in t
>> he component repository: org.codehaus.plexus.webdav.DavServerManager
>> (lookup rea
>> lm: ClassRealm[plexus.core, parent: null]).
>>
>> It doesn't look like it's getting as far as trying to proxy.
>>
>> --Wendy
>
Re: proxying was: two 500 errors
Posted by Brett Porter <br...@apache.org>.
This seems to be the same problem that a couple of other users have
reported for /repository. I'm CCing Andy in case he recognises it
(not sure if he is on this list?).
- Brett
On 29/01/2007, at 4:46 AM, Wendy Smoak wrote:
> On 1/28/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
>> Those wiki docs are now incorrect.
>> The /proxy/ URL was removed as it didn't support security or
>> webdav or
>> the ability to upload content on.
>> Having 2 URLs to access the repository was confusing.
>>
>> I'll update the wiki (and the archiva-site docs) to reflect the
>> current
>> usage.
>
> Okay, with r500200, the /proxy url no longer works. (There is no
> Action mapped for namespace / and action name proxy.)
>
> However, proxying also does not work with the the /repository URL.
>
> I have central proxied through 'myrepo', and the guest user is a
> repository observer.
>
> 1. rm -rf $M2_REPO/junit
> 2. override 'central' with url http://localhost:9091/archiva/
> repository/myrepo/
> 2. quickstart archetype ... mvn install
>
> The build fails due to the missing JUnit dependency, and the
> Archiva logs show:
>
> INFO | jvm 1 | 2007/01/28 10:34:01 | WARNING: /archiva/
> repository/myrepo/ju
> nit/junit/3.8.1/junit-3.8.1.jar:
> INFO | jvm 1 | 2007/01/28 10:34:01 |
> org.codehaus.plexus.component.reposito
> ry.exception.ComponentLookupException: Component descriptor cannot
> be found in t
> he component repository:
> org.codehaus.plexus.webdav.DavServerManager (lookup rea
> lm: ClassRealm[plexus.core, parent: null]).
>
> It doesn't look like it's getting as far as trying to proxy.
>
> --
> Wendy
Re: proxying was: two 500 errors
Posted by Andrew Williams <an...@handyande.co.uk>.
OK, I can finally replicate it.
We are working on fixing it now - related to some recent appserver
fixes I believe.
It should be working fine when executed as mvn jetty:run
Andy
On 29 Jan 2007, at 20:11, Wendy Smoak wrote:
> On 1/29/07, Andrew Williams <an...@handyande.co.uk> wrote:
>
>> Are you using bretts latest changes for archiva to use the latest
>> plexus
>> container?
>
> I re-build at last changed revision 500951 (which includes brett's
> plexus version number changes.)
>
> Same thing, error 500 on any /repository url.
>
> Here's another stack trace and list of Plexus jars:
> http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/ArchivaError20070129
>
> --
> Wendy
>
Re: proxying was: two 500 errors
Posted by Wendy Smoak <ws...@gmail.com>.
On 1/29/07, Andrew Williams <an...@handyande.co.uk> wrote:
> Are you using bretts latest changes for archiva to use the latest plexus
> container?
I re-build at last changed revision 500951 (which includes brett's
plexus version number changes.)
Same thing, error 500 on any /repository url.
Here's another stack trace and list of Plexus jars:
http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/ArchivaError20070129
--
Wendy
Re: proxying was: two 500 errors
Posted by Andrew Williams <an...@handyande.co.uk>.
hmm, actually - seems that the lookup is on the wrong realm - so
somewhere in that trace the webapp loader is passing lookups back to the
appserver - bad, I need to find where.
Are you using bretts latest changes for archiva to use the latest plexus
container?
Andy
Wendy Smoak wrote:
> Joakim,
>
> I re-built Archiva with the new plexus-webdav snapshots, but I still
> get the same error 500:
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | Jan 28, 2007 9:22:32 PM
> org.mortbay.jetty.servlet.ServletHandler$Context log
> INFO | jvm 1 | 2007/01/28 21:22:32 | INFO: Plexus container
> already in context.
> INFO | jvm 1 | 2007/01/28 21:22:32 | Jan 28, 2007 9:22:32 PM
> org.mortbay.jetty.servlet.ServletHandler handle
> INFO | jvm 1 | 2007/01/28 21:22:32 | WARNING:
> /archiva/repository/myrepo/:
> INFO | jvm 1 | 2007/01/28 21:22:32 |
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
>
> Component descriptor cannot be found in the component repository:
> org.codehaus.plexus.webdav.DavServerManager (lookup realm:
> ClassRealm[plexus.core, parent: null]).
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:93)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:313)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.codehaus.plexus.webdav.servlet.AbstractWebDavServlet.lookup(AbstractWebDavServlet.java:154)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.codehaus.plexus.webdav.servlet.AbstractWebDavServlet.initComponents(AbstractWebDavServlet.java:95)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.apache.maven.archiva.web.repository.RepositoryServlet.initComponents(RepositoryServlet.java:85)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.codehaus.plexus.webdav.servlet.AbstractWebDavServlet.init(AbstractWebDavServlet.java:89)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.init(MultiplexedWebDavServlet.java:54)
>
> INFO | jvm 1 | 2007/01/28 21:22:32 | at
> org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:383)
>
>
> Full stack trace and list of plexus jars here:
> http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/ArchivaError20070128
>
Re: proxying was: two 500 errors
Posted by Wendy Smoak <ws...@gmail.com>.
Joakim,
I re-built Archiva with the new plexus-webdav snapshots, but I still
get the same error 500:
INFO | jvm 1 | 2007/01/28 21:22:32 | Jan 28, 2007 9:22:32 PM
org.mortbay.jetty.servlet.ServletHandler$Context log
INFO | jvm 1 | 2007/01/28 21:22:32 | INFO: Plexus container
already in context.
INFO | jvm 1 | 2007/01/28 21:22:32 | Jan 28, 2007 9:22:32 PM
org.mortbay.jetty.servlet.ServletHandler handle
INFO | jvm 1 | 2007/01/28 21:22:32 | WARNING: /archiva/repository/myrepo/:
INFO | jvm 1 | 2007/01/28 21:22:32 |
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component repository:
org.codehaus.plexus.webdav.DavServerManager (lookup realm:
ClassRealm[plexus.core, parent: null]).
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:93)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:313)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:291)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.codehaus.plexus.webdav.servlet.AbstractWebDavServlet.lookup(AbstractWebDavServlet.java:154)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.codehaus.plexus.webdav.servlet.AbstractWebDavServlet.initComponents(AbstractWebDavServlet.java:95)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.apache.maven.archiva.web.repository.RepositoryServlet.initComponents(RepositoryServlet.java:85)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.codehaus.plexus.webdav.servlet.AbstractWebDavServlet.init(AbstractWebDavServlet.java:89)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.codehaus.plexus.webdav.servlet.multiplexed.MultiplexedWebDavServlet.init(MultiplexedWebDavServlet.java:54)
INFO | jvm 1 | 2007/01/28 21:22:32 | at
org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:383)
Full stack trace and list of plexus jars here:
http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/ArchivaError20070128
--
Wendy
Re: proxying was: two 500 errors
Posted by Wendy Smoak <ws...@gmail.com>.
On 1/28/07, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> Those wiki docs are now incorrect.
> The /proxy/ URL was removed as it didn't support security or webdav or
> the ability to upload content on.
> Having 2 URLs to access the repository was confusing.
>
> I'll update the wiki (and the archiva-site docs) to reflect the current
> usage.
Okay, with r500200, the /proxy url no longer works. (There is no
Action mapped for namespace / and action name proxy.)
However, proxying also does not work with the the /repository URL.
I have central proxied through 'myrepo', and the guest user is a
repository observer.
1. rm -rf $M2_REPO/junit
2. override 'central' with url http://localhost:9091/archiva/repository/myrepo/
2. quickstart archetype ... mvn install
The build fails due to the missing JUnit dependency, and the Archiva logs show:
INFO | jvm 1 | 2007/01/28 10:34:01 | WARNING: /archiva/repository/myrepo/ju
nit/junit/3.8.1/junit-3.8.1.jar:
INFO | jvm 1 | 2007/01/28 10:34:01 | org.codehaus.plexus.component.reposito
ry.exception.ComponentLookupException: Component descriptor cannot be found in t
he component repository: org.codehaus.plexus.webdav.DavServerManager (lookup rea
lm: ClassRealm[plexus.core, parent: null]).
It doesn't look like it's getting as far as trying to proxy.
--
Wendy
Re: proxying was: two 500 errors
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Those wiki docs are now incorrect.
The /proxy/ URL was removed as it didn't support security or webdav or
the ability to upload content on.
Having 2 URLs to access the repository was confusing.
I'll update the wiki (and the archiva-site docs) to reflect the current
usage.
- Joakim
Brett Porter wrote:
> Joakim,
>
> Was this something that was changed?
>
> - Brett
>
> On 28/01/2007, at 9:37 AM, Wendy Smoak wrote:
>
>> On 1/27/07, Brett Porter <br...@apache.org> wrote:
>>
>>> The instructions are incorrect - you acccess via the /repository/
>>> URL, which can be configured inside Archiva to proxy an external
>>> repository. Where did you see these instructions?
>>
>> http://docs.codehaus.org/display/MAVENUSER/Archiva+as+a+Proxy
>>
>> IME, unless you use the /proxy url, Archiva will not actually proxy
>> the requests. Could be that's fixed now, this was a while ago.
>>
>> --
>> Wendy
>