You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Max Bowsher <ma...@mxtelecom.com> on 2006/12/06 11:46:33 UTC

Archiva deployment on Jetty?

Does anyone have a working configuration of Archiva deployed on Jetty,
for which they'd be willing to share the Jetty config files?

(I'm referring to deployment on a standalone Jetty, here, rather than
testing via maven-jetty-plugin).

I've tried to get this working myself, but only succeeded by configuring
the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
that configuration to the main Jetty config so that I do not have to
poke around inside the Archiva war, I can't get the JNDI bindings to
work right.


Thanks,
Max.

Re: Archiva deployment on Jetty?

Posted by Wendy Smoak <ws...@gmail.com>.
On 12/6/06, Emmanuel Venisse <em...@venisse.net> wrote:

> It would be cool to add it in the site.

:)  http://docs.codehaus.org/display/MAVENUSER/Archiva+FAQ

-- 
Wendy

Re: Archiva deployment on Jetty?

Posted by Emmanuel Venisse <em...@venisse.net>.
Joakim,

It would be cool to add it in the site.

Emmanuel

Joakim Erdfelt a écrit :
> I have it working with jetty 6.0.2
> 
> 1) downloaded jetty 6.0.2
> 2) installed default jetty 6.0.2
> 3) removed all content under webapps/*
> 4) unpacked archiva war file into webapps/archiva/
> 5) copied jetty-env.xml into webapps/archiva/WEB-INF/jetty-env.xml
> 6) modified default port in jetty.xml
> 7) Started up with following command.
> 
> [archiva@~/java/jetty-6.0.2]$ java -Xmx256m -jar start.jar etc/jetty.xml
> etc/jetty-plus.xml
> 
> NOTE: The jetty-plus configuration is *REQUIRED* to get jndi binding to
> work.
> 
> - Joakim Erdfelt
> 
> 
> Max Bowsher wrote:
>> Does anyone have a working configuration of Archiva deployed on Jetty,
>> for which they'd be willing to share the Jetty config files?
>>
>> (I'm referring to deployment on a standalone Jetty, here, rather than
>> testing via maven-jetty-plugin).
>>
>> I've tried to get this working myself, but only succeeded by configuring
>> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
>> that configuration to the main Jetty config so that I do not have to
>> poke around inside the Archiva war, I can't get the JNDI bindings to
>> work right.
>>
>>
>> Thanks,
>> Max.
>>
>>   
> 
> 
> 
>

Re: Archiva deployment on Jetty?

Posted by drekka <de...@aegeon.com.au>.
How did you get it going ? I tried this as per the example here and on the
FAQ and it was a complete failure. Here's what I did:

1. Install the j2ee connector.
2. Checkout the svn repository to my local machine.
3. in eclipse, did a maven2 install to build it.
4. On the target machine, installed jetty 6.0.2 and wiped it's webapps
directory. Didn't do anything else.
5. Uploaded archiva-webapp/target/ to the target machines
jetty-6.0.2/webapps directory.
6. unwar'd the war.
7. updated etc/jetty.xml to a port of 2222.
8. Step 5 - copy jetty-env.xml - where is it ???? 
9. Found jetty-env.xml in my local machines archiva-webapp/src and uploaded
it to jetty-6.0.2/webapps/archiva/WEB-INF. Why wasn't this in the war ????
10. Ran the startup command.
11. Got messages about failures to find JNDI datasources but they appear to
be related to test-jndi webapp.
12. Opened target machines port 2222/archiva
13. Got a bunch of exceptions with the main cause being that the JNDI name
env/jdbc/users was not found.

So how do I fix this ??? It looks very much to me like the instructions as
given are incomplete and make assumptions about the war, or the jetty setup
or the machine or something. 

ciao
Derek.


Joakim Erdfelt-2 wrote:
> 
> I have it working with jetty 6.0.2
> 
> 1) downloaded jetty 6.0.2
> 2) installed default jetty 6.0.2
> 3) removed all content under webapps/*
> 4) unpacked archiva war file into webapps/archiva/
> 5) copied jetty-env.xml into webapps/archiva/WEB-INF/jetty-env.xml
> 6) modified default port in jetty.xml
> 7) Started up with following command.
> 
> [archiva@~/java/jetty-6.0.2]$ java -Xmx256m -jar start.jar etc/jetty.xml
> etc/jetty-plus.xml
> 
> NOTE: The jetty-plus configuration is *REQUIRED* to get jndi binding to
> work.
> 
> - Joakim Erdfelt
> 
> 
> Max Bowsher wrote:
>> Does anyone have a working configuration of Archiva deployed on Jetty,
>> for which they'd be willing to share the Jetty config files?
>>
>> (I'm referring to deployment on a standalone Jetty, here, rather than
>> testing via maven-jetty-plugin).
>>
>> I've tried to get this working myself, but only succeeded by configuring
>> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
>> that configuration to the main Jetty config so that I do not have to
>> poke around inside the Archiva war, I can't get the JNDI bindings to
>> work right.
>>
>>
>> Thanks,
>> Max.
>>
>>   
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Archiva-deployment-on-Jetty--tf2767295.html#a8153273
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Archiva deployment on Jetty?

Posted by Max Bowsher <ma...@mxtelecom.com>.
Joakim Erdfelt wrote:
> I have it working with jetty 6.0.2
> 
> 1) downloaded jetty 6.0.2
> 2) installed default jetty 6.0.2
> 3) removed all content under webapps/*
> 4) unpacked archiva war file into webapps/archiva/
> 5) copied jetty-env.xml into webapps/archiva/WEB-INF/jetty-env.xml
> 6) modified default port in jetty.xml
> 7) Started up with following command.
> 
> [archiva@~/java/jetty-6.0.2]$ java -Xmx256m -jar start.jar etc/jetty.xml
> etc/jetty-plus.xml
> 
> NOTE: The jetty-plus configuration is *REQUIRED* to get jndi binding to
> work.

I too have had it working that way.

However, people in #archiva suggest that using WEB-INF/jetty-env.xml is
not the proper way to configure it.

I'm hoping to find a way to configure it which doesn't involve tweaking
the war.

Max.

Re: Archiva deployment on Jetty?

Posted by Joakim Erdfelt <jo...@erdfelt.com>.
I have it working with jetty 6.0.2

1) downloaded jetty 6.0.2
2) installed default jetty 6.0.2
3) removed all content under webapps/*
4) unpacked archiva war file into webapps/archiva/
5) copied jetty-env.xml into webapps/archiva/WEB-INF/jetty-env.xml
6) modified default port in jetty.xml
7) Started up with following command.

[archiva@~/java/jetty-6.0.2]$ java -Xmx256m -jar start.jar etc/jetty.xml
etc/jetty-plus.xml

NOTE: The jetty-plus configuration is *REQUIRED* to get jndi binding to
work.

- Joakim Erdfelt


Max Bowsher wrote:
> Does anyone have a working configuration of Archiva deployed on Jetty,
> for which they'd be willing to share the Jetty config files?
>
> (I'm referring to deployment on a standalone Jetty, here, rather than
> testing via maven-jetty-plugin).
>
> I've tried to get this working myself, but only succeeded by configuring
> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
> that configuration to the main Jetty config so that I do not have to
> poke around inside the Archiva war, I can't get the JNDI bindings to
> work right.
>
>
> Thanks,
> Max.
>
>

Re: Archiva deployment on Jetty?

Posted by Max Bowsher <ma...@mxtelecom.com>.
Emmanuel Venisse wrote:
> what do you have in your jetty.xml?

My jetty.xml is completely unmodified from what shipped with jetty.
Then, I have jetty-archiva.xml with content as below, and am invoking
jetty as:
  java -jar start.jar etc/jetty.xml etc/jetty-archiva.xml

<Configure id="Server" class="org.mortbay.jetty.Server">

  <Array id="plusConfig" type="java.lang.String">
    <Item>org.mortbay.jetty.webapp.WebInfConfiguration</Item>
    <Item>org.mortbay.jetty.plus.webapp.EnvConfiguration</Item>
    <Item>org.mortbay.jetty.plus.webapp.Configuration</Item>
    <Item>org.mortbay.jetty.webapp.JettyWebXmlConfiguration</Item>
    <Item>org.mortbay.jetty.webapp.TagLibConfiguration</Item>
  </Array>

  <Call class="org.mortbay.jetty.webapp.WebAppContext"
name="addWebApplications">
    <Arg><Ref id="contexts"/></Arg>
    <Arg>../webapps</Arg>
    <Arg>org/mortbay/jetty/webapp/webdefault.xml</Arg>
    <Arg><Ref id="plusConfig"/></Arg>
    <Arg type="boolean">True</Arg>
    <Arg type="boolean">False</Arg>
  </Call>

  <Call class="java.lang.System" name="setProperty">
    <Arg>derby.system.home</Arg>
    <Arg><SystemProperty name="java.io.tmpdir"/></Arg>
  </Call>

  <New class="org.mortbay.jetty.plus.naming.Resource">
    <Arg>jdbc/users</Arg>
    <Arg>
      <New class="org.apache.derby.jdbc.EmbeddedDataSource">
        <Set name="DatabaseName">target/database</Set>
        <Set name="user">sa</Set>
        <Set name="createDatabase">create</Set>
      </New>
    </Arg>
  </New>

  <New class="org.mortbay.jetty.plus.naming.Resource">
    <Arg>jdbc/shutdown</Arg>
    <Arg>
      <New class="org.apache.derby.jdbc.EmbeddedDataSource">
        <Set name="DatabaseName">target/database</Set>
        <Set name="user">sa</Set>
        <Set name="shutdownDatabase">shutdown</Set>
      </New>
    </Arg>
  </New>

</Configure>


> Max Bowsher a écrit :
>> Emmanuel Venisse wrote:
>>> you need to put derby jar in jetty lib
>>
>> Done that. It's starting up fine.
>>
>> However, on the first HTTP request, it all falls over (exception below).
>> Therefore, I'm hoping for a known-good config to identify what I'm doing
>> wrong.
[snipped exception]

>>> Max Bowsher a écrit :
>>>> Does anyone have a working configuration of Archiva deployed on Jetty,
>>>> for which they'd be willing to share the Jetty config files?
>>>>
>>>> (I'm referring to deployment on a standalone Jetty, here, rather than
>>>> testing via maven-jetty-plugin).
>>>>
>>>> I've tried to get this working myself, but only succeeded by
>>>> configuring
>>>> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
>>>> that configuration to the main Jetty config so that I do not have to
>>>> poke around inside the Archiva war, I can't get the JNDI bindings to
>>>> work right.

Re: Archiva deployment on Jetty?

Posted by Emmanuel Venisse <em...@venisse.net>.
what do you have in your jetty.xml?

Max Bowsher a écrit :
> Emmanuel Venisse wrote:
>> you need to put derby jar in jetty lib
> 
> Done that. It's starting up fine.
> 
> However, on the first HTTP request, it all falls over (exception below).
> Therefore, I'm hoping for a known-good config to identify what I'm doing
> wrong.
> 
> Max.
> 
> 
> Caught Exception while registering Interceptor class
> pssForceAdminUserInterceptor - [unknown location]
> 	at
> org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:134)
> 	at
> com.opensymphony.xwork.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:48)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.lookupInterceptorReference(XmlConfigurationProvider.java:702)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStack(XmlConfigurationProvider.java:569)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStacks(XmlConfigurationProvider.java:582)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptors(XmlConfigurationProvider.java:603)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.addPackage(XmlConfigurationProvider.java:204)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadConfigurationFile(XmlConfigurationProvider.java:676)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadConfigurationFile(XmlConfigurationProvider.java:679)
> 	at
> com.opensymphony.xwork.config.providers.XmlConfigurationProvider.init(XmlConfigurationProvider.java:91)
> 	at
> com.opensymphony.xwork.config.impl.DefaultConfiguration.reload(DefaultConfiguration.java:85)
> 	at
> com.opensymphony.xwork.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:54)
> 	at com.opensymphony.xwork.DefaultActionProxy.(DefaultActionProxy.java:57)
> 	at
> com.opensymphony.xwork.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:46)
> 	at
> com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:216)
> 	at
> com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
> 	at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
> 	at
> com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
> 	at
> com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
> 	at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
> 	at
> com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
> 	at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:358)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629)
>  	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:453)
> 	at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
> 	at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> 	at org.mortbay.jetty.Server.handle(Server.java:303)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)
> 	at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:721)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:509)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)
> 	at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:320)
> 	at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
> Caused by: org.jpox.exceptions.ConnectionFactoryNotFoundException:
> Connection Factory "java:comp/env/jdbc/users" not found
> NestedThrowables:
> javax.naming.NameNotFoundException; remaining name 'jdbc/users'
> 	at
> org.jpox.AbstractPersistenceManagerFactory.lookupDataSource(AbstractPersistenceManagerFactory.java:175)
> 	at
> org.jpox.AbstractPersistenceManagerFactory.freezeConfiguration(AbstractPersistenceManagerFactory.java:212)
> 	at
> org.jpox.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:99)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:534)
> 	at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:478)
> 	at
> org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.doConfigure(AbstractConfigurableJdoFactory.java:134)
> 	at
> org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.configure(AbstractConfigurableJdoFactory.java:101)
>  	at
> org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.getPersistenceManagerFactory(AbstractConfigurableJdoFactory.java:64)
> 	at
> org.codehaus.plexus.security.user.jdo.JdoUserManager.initialize(JdoUserManager.java:307)
> 	at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:16)
> 	at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:102)
> 	at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:110)
> 	at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:100)
> 	at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
> 	at
> org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:77)
> 	at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:247)
> 	at
> org.codehaus.plexus.component.composition.CompositionUtils.findRequirement(CompositionUtils.java:87)
> 	at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:70)
> 	at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirement(FieldComponentComposer.java:61)
> 	at
> org.codehaus.plexus.component.composition.AbstractComponentComposer.assembleComponent(AbstractComponentComposer.java:103)
> 	at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:70)
> 	at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:31)
> 	at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:102)
> 	at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:110)
> 	at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:100)
> 	at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
> 	at
> org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:77)
> 	at
> org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:191)
> 	at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:265)
> 	at
> org.codehaus.plexus.xwork.PlexusObjectFactory.lookup(PlexusObjectFactory.java:390)
> 	at
> org.codehaus.plexus.xwork.PlexusObjectFactory.loadComponentWithPlexus(PlexusObjectFactory.java:346)
> 	at
> org.codehaus.plexus.xwork.PlexusObjectFactory.lookup(PlexusObjectFactory.java:326)
> 	at
> org.codehaus.plexus.xwork.PlexusObjectFactory.buildBean(PlexusObjectFactory.java:170)
> 	at
> org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:99)
> 	... 36 more
> Caused by: javax.naming.NameNotFoundException; remaining name 'jdbc/users'
> 	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:634)
> 	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:665)
> 	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:665)
> 	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:680)
> 	at
> org.mortbay.naming.java.javaRootURLContext.lookup(javaRootURLContext.java:112)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:351)
> 	at
> org.jpox.AbstractPersistenceManagerFactory.lookupDataSource(AbstractPersistenceManagerFactory.java:171)
> 	... 73 more
> 
> 
> 
>> Max Bowsher a écrit :
>>> Does anyone have a working configuration of Archiva deployed on Jetty,
>>> for which they'd be willing to share the Jetty config files?
>>>
>>> (I'm referring to deployment on a standalone Jetty, here, rather than
>>> testing via maven-jetty-plugin).
>>>
>>> I've tried to get this working myself, but only succeeded by configuring
>>> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
>>> that configuration to the main Jetty config so that I do not have to
>>> poke around inside the Archiva war, I can't get the JNDI bindings to
>>> work right.
> 
> 
>

Re: Archiva deployment on Jetty?

Posted by Max Bowsher <ma...@mxtelecom.com>.
Emmanuel Venisse wrote:
> you need to put derby jar in jetty lib

Done that. It's starting up fine.

However, on the first HTTP request, it all falls over (exception below).
Therefore, I'm hoping for a known-good config to identify what I'm doing
wrong.

Max.


Caught Exception while registering Interceptor class
pssForceAdminUserInterceptor - [unknown location]
	at
org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:134)
	at
com.opensymphony.xwork.config.providers.InterceptorBuilder.constructInterceptorReference(InterceptorBuilder.java:48)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.lookupInterceptorReference(XmlConfigurationProvider.java:702)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStack(XmlConfigurationProvider.java:569)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStacks(XmlConfigurationProvider.java:582)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptors(XmlConfigurationProvider.java:603)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.addPackage(XmlConfigurationProvider.java:204)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadConfigurationFile(XmlConfigurationProvider.java:676)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadConfigurationFile(XmlConfigurationProvider.java:679)
	at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.init(XmlConfigurationProvider.java:91)
	at
com.opensymphony.xwork.config.impl.DefaultConfiguration.reload(DefaultConfiguration.java:85)
	at
com.opensymphony.xwork.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:54)
	at com.opensymphony.xwork.DefaultActionProxy.(DefaultActionProxy.java:57)
	at
com.opensymphony.xwork.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:46)
	at
com.opensymphony.webwork.dispatcher.DispatcherUtils.serviceAction(DispatcherUtils.java:216)
	at
com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:202)
	at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
	at
com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)
	at
com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)
	at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
	at
com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(ActionContextCleanUp.java:88)
	at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1045)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:358)
	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629)
 	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:453)
	at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
	at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
	at org.mortbay.jetty.Server.handle(Server.java:303)
	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)
	at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:721)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:509)
	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)
	at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:320)
	at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: org.jpox.exceptions.ConnectionFactoryNotFoundException:
Connection Factory "java:comp/env/jdbc/users" not found
NestedThrowables:
javax.naming.NameNotFoundException; remaining name 'jdbc/users'
	at
org.jpox.AbstractPersistenceManagerFactory.lookupDataSource(AbstractPersistenceManagerFactory.java:175)
	at
org.jpox.AbstractPersistenceManagerFactory.freezeConfiguration(AbstractPersistenceManagerFactory.java:212)
	at
org.jpox.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:99)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:534)
	at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:478)
	at
org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.doConfigure(AbstractConfigurableJdoFactory.java:134)
	at
org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.configure(AbstractConfigurableJdoFactory.java:101)
 	at
org.codehaus.plexus.jdo.AbstractConfigurableJdoFactory.getPersistenceManagerFactory(AbstractConfigurableJdoFactory.java:64)
	at
org.codehaus.plexus.security.user.jdo.JdoUserManager.initialize(JdoUserManager.java:307)
	at
org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:16)
	at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:102)
	at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:110)
	at
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:100)
	at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
	at
org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:77)
	at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:247)
	at
org.codehaus.plexus.component.composition.CompositionUtils.findRequirement(CompositionUtils.java:87)
	at
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:70)
	at
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirement(FieldComponentComposer.java:61)
	at
org.codehaus.plexus.component.composition.AbstractComponentComposer.assembleComponent(AbstractComponentComposer.java:103)
	at
org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:70)
	at
org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:31)
	at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:102)
	at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:110)
	at
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:100)
	at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
	at
org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:77)
	at
org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:191)
	at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:265)
	at
org.codehaus.plexus.xwork.PlexusObjectFactory.lookup(PlexusObjectFactory.java:390)
	at
org.codehaus.plexus.xwork.PlexusObjectFactory.loadComponentWithPlexus(PlexusObjectFactory.java:346)
	at
org.codehaus.plexus.xwork.PlexusObjectFactory.lookup(PlexusObjectFactory.java:326)
	at
org.codehaus.plexus.xwork.PlexusObjectFactory.buildBean(PlexusObjectFactory.java:170)
	at
org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(PlexusObjectFactory.java:99)
	... 36 more
Caused by: javax.naming.NameNotFoundException; remaining name 'jdbc/users'
	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:634)
	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:665)
	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:665)
	at org.mortbay.naming.NamingContext.lookup(NamingContext.java:680)
	at
org.mortbay.naming.java.javaRootURLContext.lookup(javaRootURLContext.java:112)
	at javax.naming.InitialContext.lookup(InitialContext.java:351)
	at
org.jpox.AbstractPersistenceManagerFactory.lookupDataSource(AbstractPersistenceManagerFactory.java:171)
	... 73 more



> Max Bowsher a écrit :
>> Does anyone have a working configuration of Archiva deployed on Jetty,
>> for which they'd be willing to share the Jetty config files?
>>
>> (I'm referring to deployment on a standalone Jetty, here, rather than
>> testing via maven-jetty-plugin).
>>
>> I've tried to get this working myself, but only succeeded by configuring
>> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
>> that configuration to the main Jetty config so that I do not have to
>> poke around inside the Archiva war, I can't get the JNDI bindings to
>> work right.

Re: Archiva deployment on Jetty?

Posted by Emmanuel Venisse <em...@venisse.net>.
you need to put derby jar in jetty lib

Emmanuel

Max Bowsher a écrit :
> Does anyone have a working configuration of Archiva deployed on Jetty,
> for which they'd be willing to share the Jetty config files?
> 
> (I'm referring to deployment on a standalone Jetty, here, rather than
> testing via maven-jetty-plugin).
> 
> I've tried to get this working myself, but only succeeded by configuring
> the JNDI datasource stuff via WEB-INF/jetty-env.xml. When I try to move
> that configuration to the main Jetty config so that I do not have to
> poke around inside the Archiva war, I can't get the JNDI bindings to
> work right.
> 
> 
> Thanks,
> Max.
> 
> 
>