You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Peter Klotz <pe...@blue-elephant-systems.com> on 2006/08/24 12:01:17 UTC

ClientFactory in snapshot 23.8 JNDI issue

The new ClientFactory mechanism should be in the latest snapshot?

    try
    {
      Hashtable env = new Hashtable();
      env.put(Context.INITIAL_CONTEXT_FACTORY, this.jndiInitialContextFactory);
      env.put(Context.PROVIDER_URL, jndiProviderUrl);

      Context ctx = new InitialContext(env);
      Object obj = ctx.lookup(ClientFactory.DEFAULT_JNDI_NAME);
      if (obj != null)
      {
        // found JBI container in JNDI
        // create default servicemix client
        ClientFactory clientFactory = (ClientFactory) obj;
        client = clientFactory.createClient();
        resolver = client.createResolverForService(new QName(NS_URL, service,
NS_PREFIX));
      }
    } catch (NamingException e)
    {
      getLogger().debug("NamingException when creating DefaultServiceMixClient", e);
    } catch (JBIException e)
    {
      getLogger().debug("JBIException when creating DefaultServiceMixClient", e);
    }


And still we get JNDI problems. The code above runs in a SU (inside jetty,
Cocoon) and thus has the full SM classpath available. Any ideas?



DEBUG   (2006-08-24) 11:18.57:530   [core.midas] (Unknown-URI)
Unknown-Thread/DOServiceMixClient: NamingException when creating
DefaultServiceMixClient
javax.naming.NamingException: scheme java not recognized
	at org.apache.xbean.spring.jndi.DefaultContext.lookup(DefaultContext.java:131)
	at javax.naming.InitialContext.lookup(InitialContext.java:347)
	at
com.bes.itm.cocoon.servicemix.DOServiceMixClient.initialize(DOServiceMixClient.java:107)
	at
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
	at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:297)
	at
org.apache.avalon.excalibur.component.DefaultComponentHandler.doGet(DefaultComponentHandler.java:136)
	at
org.apache.avalon.excalibur.component.ComponentHandler.get(ComponentHandler.java:381)
	at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:279)
	at
org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:335)
	at
org.apache.avalon.framework.service.WrapperServiceManager.lookup(WrapperServiceManager.java:68)
	at com.bes.itm.cocoon.openadaptor.AdaptorClient.service(AdaptorClient.java:133)
	at
org.apache.avalon.framework.container.ContainerUtil.service(ContainerUtil.java:143)
	at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:271)
	at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
	at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:278)
	at
org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:335)
	at
org.apache.avalon.framework.service.WrapperServiceManager.lookup(WrapperServiceManager.java:68)
	at com.bes.itm.cocoon.backend.BackendModule.service(BackendModule.java:72)
	at
org.apache.avalon.framework.container.ContainerUtil.service(ContainerUtil.java:143)
	at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:271)
	at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
	at
org.apache.avalon.excalibur.component.ExcaliburComponentSelector.addComponent(ExcaliburComponentSelector.java:705)
	at
org.apache.cocoon.components.ExtendedComponentSelector.configure(ExtendedComponentSelector.java:228)
	at
org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:201)
	at
org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:289)
	at
org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:108)
	at
org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:524)
	at
org.apache.cocoon.components.CocoonComponentManager.initialize(CocoonComponentManager.java:566)
	at
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
	at org.apache.cocoon.Cocoon.initialize(Cocoon.java:342)
	at
org.apache.avalon.framework.container.ContainerUtil.initialize(ContainerUtil.java:244)
	at org.apache.cocoon.servlet.CocoonServlet.createCocoon(CocoonServlet.java:1428)
	at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:498)
	at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:397)
	at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:252)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
	at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:570)
	at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1143)
	at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:414)
	at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
	at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
	at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:121)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
	at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
	at org.mortbay.jetty.Server.doStart(Server.java:213)
	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
	at
com.bes.itm.comp.jetty.SimpleJettyLauncher.afterPropertiesSet(SimpleJettyLauncher.java:77)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:908)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:875)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:396)
	at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:240)
	at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:132)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:237)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:153)
	at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:254)
	at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:337)
	at
org.apache.xbean.server.spring.configuration.SpringConfiguration.<init>(SpringConfiguration.java:63)
	at
org.apache.xbean.server.spring.configuration.SpringConfigurationServiceFactory.createService(SpringConfigurationServiceFactory.java:106)
	at org.apache.xbean.kernel.standard.ServiceManager.start(ServiceManager.java:420)
	at
org.apache.xbean.kernel.standard.ServiceManager.initialize(ServiceManager.java:200)
	at
org.apache.xbean.kernel.standard.RegistryFutureTask$RegisterCallable.call(RegistryFutureTask.java:110)
	at
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
	at
org.apache.xbean.kernel.standard.ServiceManagerRegistry.registerService(ServiceManagerRegistry.java:409)
	at
org.apache.xbean.kernel.standard.StandardKernel.registerService(StandardKernel.java:220)
	at org.apache.xbean.server.spring.loader.SpringLoader.load(SpringLoader.java:154)
	at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:81)
	at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
	at
org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:107)
	at
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
	at
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:121)
	at
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCycle.java:328)
	at
org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:97)
	at org.apache.servicemix.jbi.container.JBIContainer.start(JBIContainer.java:564)
	at
org.apache.servicemix.jbi.container.SpringJBIContainer.afterPropertiesSet(SpringJBIContainer.java:79)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:908)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:875)
	at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:396)
	at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:240)
	at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:132)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:237)
	at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:153)
	at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:254)
	at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:337)
	at
org.apache.xbean.spring.context.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:162)
	at
org.apache.xbean.spring.context.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:52)
	at org.apache.servicemix.Main.main(Main.java:53)
	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:324)
	at org.codehaus.classworlds.Launcher.launchStandard(Launcher.java:410)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:344)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:461)
	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:324)
	at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:292)
	at java.lang.Thread.run(Thread.java:534)




Thanks, Peter

Re: ClientFactory in snapshot 23.8 JNDI issue

Posted by Guillaume Nodet <gn...@gmail.com>.
Done: http://svn.apache.org/viewvc?view=rev&revision=436782
Could you give it a try ?

On 8/25/06, Guillaume Nodet <gn...@gmail.com> wrote:
>
> Of course, it should. I will fix that asap.
>
>
> On 8/25/06, Peter Klotz <peter.klotz@blue-elephant-systems.com > wrote:
> >
> > Hi Guillaume,
> >
> > Guillaume Nodet wrote:
> > > Yeah, it may be a timing issue.
> > > The ClientFactory is initialized and started after components and sus
> > are
> > > restored to their previous state.
> > > Are you trying to access the ClientFactory from a SU ?
> >
> > yes we do access ClientFactory from a SU. There is a jetty-su that runs
> > a web
> > application and from within this web application we access JNDI to get a
> > client
> > factory and create a DefaultServiceMixClient if we are running in the
> > same SM
> > process that works fine. Just the server has to be completely started
> > before we
> > can do this obviously.
> >
> > Normally all things that are published to JNDI should have been started
> > before
> > any SUs are deployed or re-deployed? ClientFactory is a system service
> > and
> > should be there for SUs to use, could this be made so?
> >
> >
> > Thanks, Peter
> >
> >
>
>
> --
> Cheers,
> Guillaume Nodet
>



-- 
Cheers,
Guillaume Nodet

Re: ClientFactory in snapshot 23.8 JNDI issue

Posted by Guillaume Nodet <gn...@gmail.com>.
Of course, it should. I will fix that asap.

On 8/25/06, Peter Klotz <pe...@blue-elephant-systems.com> wrote:
>
> Hi Guillaume,
>
> Guillaume Nodet wrote:
> > Yeah, it may be a timing issue.
> > The ClientFactory is initialized and started after components and sus
> are
> > restored to their previous state.
> > Are you trying to access the ClientFactory from a SU ?
>
> yes we do access ClientFactory from a SU. There is a jetty-su that runs a
> web
> application and from within this web application we access JNDI to get a
> client
> factory and create a DefaultServiceMixClient if we are running in the same
> SM
> process that works fine. Just the server has to be completely started
> before we
> can do this obviously.
>
> Normally all things that are published to JNDI should have been started
> before
> any SUs are deployed or re-deployed? ClientFactory is a system service and
> should be there for SUs to use, could this be made so?
>
>
> Thanks, Peter
>
>


-- 
Cheers,
Guillaume Nodet

Re: ClientFactory in snapshot 23.8 JNDI issue

Posted by Peter Klotz <pe...@blue-elephant-systems.com>.
Hi Guillaume,

Guillaume Nodet wrote:
> Yeah, it may be a timing issue.
> The ClientFactory is initialized and started after components and sus are
> restored to their previous state.
> Are you trying to access the ClientFactory from a SU ?

yes we do access ClientFactory from a SU. There is a jetty-su that runs a web
application and from within this web application we access JNDI to get a client
factory and create a DefaultServiceMixClient if we are running in the same SM
process that works fine. Just the server has to be completely started before we
can do this obviously.

Normally all things that are published to JNDI should have been started before
any SUs are deployed or re-deployed? ClientFactory is a system service and
should be there for SUs to use, could this be made so?


Thanks, Peter

Re: MBeans

Posted by Guillaume Nodet <gn...@gmail.com>.
A component can register mbeans when initialized and unregister
them when shutdown, using the following helper class to
create the mbean name:
http://incubator.apache.org/servicemix/maven/servicemix-jbi/apidocs/javax/jbi/management/MBeanNames.html
which can be retrieved on the component context.

Else, you can register any mbean you want using spring, or direct mbean
calls,
but there' s no specific stuff to deploy such things as in JBoss.  Though
you may be able to leverage servicemix-lwcontainer and deploy a spring
file to register your mbeans (though you will need to deploy at least a
dummy activation spec).

On 8/24/06, Thomas TERMIN <tt...@blue-elephant-systems.com> wrote:
>
> Hello,
>
> Is there a concept to register own MBeans in servicemix? For example
> like in JBoss as a service deployment.
>
> Regards
> Thomas
>
>


-- 
Cheers,
Guillaume Nodet

MBeans

Posted by Thomas TERMIN <tt...@blue-elephant-systems.com>.
Hello,

Is there a concept to register own MBeans in servicemix? For example 
like in JBoss as a service deployment.

Regards
Thomas


Re: ClientFactory in snapshot 23.8 JNDI issue

Posted by Guillaume Nodet <gn...@gmail.com>.
Yeah, it may be a timing issue.
The ClientFactory is initialized and started after components and sus are
restored to their previous state.
Are you trying to access the ClientFactory from a SU ?

On 8/24/06, Peter Klotz <pe...@blue-elephant-systems.com> wrote:
>
> Guillaume Nodet wrote:
> > Could you explain how servicemix is deployed, and where do you try
> > to access the client factory from ? From another web app in the same
> > jetty container ?
> > Or if you have a working (i should say non-working) example,
> > it would be even better.
>
> Obviously it was a timing issue, when I moved the creation of the
> ServiceMixClient to runtime instead of initialization time it works fine
> always.
> Otherwise the problem did not occur always but only sometimes or on some
> machines evtl. slower ones.
>
> Could it be that the JNDI publishing is done after some of the SUs are
> already
> deployed?
>
>
> Peter
>
>


-- 
Cheers,
Guillaume Nodet

Re: ClientFactory in snapshot 23.8 JNDI issue

Posted by Peter Klotz <pe...@blue-elephant-systems.com>.
Guillaume Nodet wrote:
> Could you explain how servicemix is deployed, and where do you try
> to access the client factory from ? From another web app in the same
> jetty container ?
> Or if you have a working (i should say non-working) example,
> it would be even better.

Obviously it was a timing issue, when I moved the creation of the
ServiceMixClient to runtime instead of initialization time it works fine always.
Otherwise the problem did not occur always but only sometimes or on some
machines evtl. slower ones.

Could it be that the JNDI publishing is done after some of the SUs are already
deployed?


Peter

Re: ClientFactory in snapshot 23.8 JNDI issue

Posted by Guillaume Nodet <gn...@gmail.com>.
Could you explain how servicemix is deployed, and where do you try
to access the client factory from ? From another web app in the same
jetty container ?
Or if you have a working (i should say non-working) example,
it would be even better.

On 8/24/06, Peter Klotz <pe...@blue-elephant-systems.com> wrote:
>
>
> The new ClientFactory mechanism should be in the latest snapshot?


Well, yes.
   org.apache.servicemix.client.ClientFactory
is inside the jar from 08/23

    try
>     {
>       Hashtable env = new Hashtable();
>       env.put(Context.INITIAL_CONTEXT_FACTORY,
> this.jndiInitialContextFactory);
>       env.put(Context.PROVIDER_URL, jndiProviderUrl);
>
>       Context ctx = new InitialContext(env);
>       Object obj = ctx.lookup(ClientFactory.DEFAULT_JNDI_NAME);
>       if (obj != null)
>       {
>         // found JBI container in JNDI
>         // create default servicemix client
>         ClientFactory clientFactory = (ClientFactory) obj;
>         client = clientFactory.createClient();
>         resolver = client.createResolverForService(new QName(NS_URL,
> service,
> NS_PREFIX));
>       }
>     } catch (NamingException e)
>     {
>       getLogger().debug("NamingException when creating
> DefaultServiceMixClient", e);
>     } catch (JBIException e)
>     {
>       getLogger().debug("JBIException when creating
> DefaultServiceMixClient", e);
>     }
>
>
> And still we get JNDI problems. The code above runs in a SU (inside jetty,
> Cocoon) and thus has the full SM classpath available. Any ideas?
>
>
>
> DEBUG   (2006-08-24) 11:18.57:530   [core.midas ] (Unknown-URI)
> Unknown-Thread/DOServiceMixClient: NamingException when creating
> DefaultServiceMixClient
> javax.naming.NamingException: scheme java not recognized
>         at org.apache.xbean.spring.jndi.DefaultContext.lookup (
> DefaultContext.java:131)
>         at javax.naming.InitialContext.lookup(InitialContext.java:347)
>         at
> com.bes.itm.cocoon.servicemix.DOServiceMixClient.initialize(
> DOServiceMixClient.java:107)
>         at
> org.apache.avalon.framework.container.ContainerUtil.initialize(
> ContainerUtil.java:244)
>         at
> org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(
> DefaultComponentFactory.java:297)
>         at
> org.apache.avalon.excalibur.component.DefaultComponentHandler.doGet(
> DefaultComponentHandler.java:136)
>         at
> org.apache.avalon.excalibur.component.ComponentHandler.get(
> ComponentHandler.java:381)
>         at
> org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(
> ExcaliburComponentManager.java:279)
>         at
> org.apache.cocoon.components.CocoonComponentManager.lookup(
> CocoonComponentManager.java:335)
>         at
> org.apache.avalon.framework.service.WrapperServiceManager.lookup(
> WrapperServiceManager.java:68)
>         at com.bes.itm.cocoon.openadaptor.AdaptorClient.service(
> AdaptorClient.java:133)
>         at
> org.apache.avalon.framework.container.ContainerUtil.service (
> ContainerUtil.java:143)
>         at
> org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(
> DefaultComponentFactory.java:271)
>         at
>
> org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(
> ThreadSafeComponentHandler.java:108)
>         at
> org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(
> ExcaliburComponentManager.java:278)
>         at
> org.apache.cocoon.components.CocoonComponentManager.lookup (
> CocoonComponentManager.java:335)
>         at
> org.apache.avalon.framework.service.WrapperServiceManager.lookup(
> WrapperServiceManager.java:68)
>         at com.bes.itm.cocoon.backend.BackendModule.service(
> BackendModule.java :72)
>         at
> org.apache.avalon.framework.container.ContainerUtil.service(
> ContainerUtil.java:143)
>         at
> org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(
> DefaultComponentFactory.java :271)
>         at
>
> org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize
> (ThreadSafeComponentHandler.java:108)
>         at
>
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector.addComponent(
> ExcaliburComponentSelector.java:705)
>         at
> org.apache.cocoon.components.ExtendedComponentSelector.configure(
> ExtendedComponentSelector.java:228)
>         at
> org.apache.avalon.framework.container.ContainerUtil.configure (
> ContainerUtil.java:201)
>         at
> org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(
> DefaultComponentFactory.java:289)
>         at
>
> org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(
> ThreadSafeComponentHandler.java:108)
>         at
> org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize
> (ExcaliburComponentManager.java:524)
>         at
> org.apache.cocoon.components.CocoonComponentManager.initialize (
> CocoonComponentManager.java:566)
>         at
> org.apache.avalon.framework.container.ContainerUtil.initialize(
> ContainerUtil.java:244)
>         at org.apache.cocoon.Cocoon.initialize(Cocoon.java:342)
>         at
> org.apache.avalon.framework.container.ContainerUtil.initialize(
> ContainerUtil.java:244)
>         at org.apache.cocoon.servlet.CocoonServlet.createCocoon(
> CocoonServlet.java:1428)
>         at org.apache.cocoon.servlet.CocoonServlet.init (
> CocoonServlet.java:498)
>         at org.mortbay.jetty.servlet.ServletHolder.initServlet(
> ServletHolder.java:397)
>         at org.mortbay.jetty.servlet.ServletHolder.doStart(
> ServletHolder.java:252)
>         at org.mortbay.component.AbstractLifeCycle.start (
> AbstractLifeCycle.java:38)
>         at org.mortbay.jetty.servlet.ServletHandler.initialize(
> ServletHandler.java:570)
>         at org.mortbay.jetty.webapp.WebAppContext.startContext(
> WebAppContext.java:1143)
>         at org.mortbay.jetty.handler.ContextHandler.doStart(
> ContextHandler.java:414)
>         at org.mortbay.jetty.webapp.WebAppContext.doStart(
> WebAppContext.java:467)
>         at org.mortbay.component.AbstractLifeCycle.start(
> AbstractLifeCycle.java :38)
>         at org.mortbay.jetty.handler.HandlerCollection.doStart(
> HandlerCollection.java:156)
>         at
> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(
> ContextHandlerCollection.java:121)
>         at org.mortbay.component.AbstractLifeCycle.start(
> AbstractLifeCycle.java:38)
>         at org.mortbay.jetty.handler.HandlerCollection.doStart(
> HandlerCollection.java:156)
>         at org.mortbay.component.AbstractLifeCycle.start (
> AbstractLifeCycle.java:38)
>         at org.mortbay.jetty.handler.HandlerWrapper.doStart(
> HandlerWrapper.java:119)
>         at org.mortbay.jetty.Server.doStart(Server.java:213)
>         at org.mortbay.component.AbstractLifeCycle.start (
> AbstractLifeCycle.java:38)
>         at
> com.bes.itm.comp.jetty.SimpleJettyLauncher.afterPropertiesSet(
> SimpleJettyLauncher.java:77)
>         at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(
> AbstractAutowireCapableBeanFactory.java:908)
>         at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
> (AbstractAutowireCapableBeanFactory.java:875)
>         at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(
> AbstractAutowireCapableBeanFactory.java:396)
>         at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(
> AbstractBeanFactory.java:240)
>         at
>
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(
> DefaultSingletonBeanRegistry.java:132)
>         at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(
> AbstractBeanFactory.java:237)
>         at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean (
> AbstractBeanFactory.java:153)
>         at
>
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons
> (DefaultListableBeanFactory.java:254)
>         at
> org.springframework.context.support.AbstractApplicationContext.refresh (
> AbstractApplicationContext.java:337)
>         at
> org.apache.xbean.server.spring.configuration.SpringConfiguration.<init>(
> SpringConfiguration.java:63)
>         at
>
> org.apache.xbean.server.spring.configuration.SpringConfigurationServiceFactory.createService(
> SpringConfigurationServiceFactory.java:106)
>         at org.apache.xbean.kernel.standard.ServiceManager.start(
> ServiceManager.java:420)
>         at
> org.apache.xbean.kernel.standard.ServiceManager.initialize(
> ServiceManager.java :200)
>         at
> org.apache.xbean.kernel.standard.RegistryFutureTask$RegisterCallable.call(
> RegistryFutureTask.java:110)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(
> FutureTask.java:176)
>         at
> org.apache.xbean.kernel.standard.ServiceManagerRegistry.registerService(
> ServiceManagerRegistry.java:409)
>         at
> org.apache.xbean.kernel.standard.StandardKernel.registerService(
> StandardKernel.java :220)
>         at org.apache.xbean.server.spring.loader.SpringLoader.load(
> SpringLoader.java:154)
>         at
> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(
> AbstractXBeanDeployer.java:81)
>         at
> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(
> BaseServiceUnitManager.java:88)
>         at
> org.apache.servicemix.common.BaseServiceUnitManager.init(
> BaseServiceUnitManager.java:107)
>         at
> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(
> ServiceUnitLifeCycle.java:85)
>         at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(
> ServiceAssemblyLifeCycle.java:121)
>         at
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(
> ServiceAssemblyLifeCycle.java:328)
>         at
> org.apache.servicemix.jbi.framework.DeploymentService.start(
> DeploymentService.java:97)
>         at org.apache.servicemix.jbi.container.JBIContainer.start(
> JBIContainer.java:564)
>         at
> org.apache.servicemix.jbi.container.SpringJBIContainer.afterPropertiesSet(
> SpringJBIContainer.java:79)
>         at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(
> AbstractAutowireCapableBeanFactory.java:908)
>         at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
> (AbstractAutowireCapableBeanFactory.java:875)
>         at
>
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(
> AbstractAutowireCapableBeanFactory.java:396)
>         at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(
> AbstractBeanFactory.java:240)
>         at
>
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(
> DefaultSingletonBeanRegistry.java:132)
>         at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(
> AbstractBeanFactory.java:237)
>         at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean (
> AbstractBeanFactory.java:153)
>         at
>
> org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons
> (DefaultListableBeanFactory.java:254)
>         at
> org.springframework.context.support.AbstractApplicationContext.refresh (
> AbstractApplicationContext.java:337)
>         at
> org.apache.xbean.spring.context.ClassPathXmlApplicationContext.<init>(
> ClassPathXmlApplicationContext.java:162)
>         at
> org.apache.xbean.spring.context.ClassPathXmlApplicationContext .<init>(
> ClassPathXmlApplicationContext.java:52)
>         at org.apache.servicemix.Main.main(Main.java:53)
>         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:324)
>         at org.codehaus.classworlds.Launcher.launchStandard (Launcher.java
> :410)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:344)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:461)
>         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:324)
>         at org.tanukisoftware.wrapper.WrapperSimpleApp.run(
> WrapperSimpleApp.java:292)
>         at java.lang.Thread.run(Thread.java:534)
>
>
>
>
> Thanks, Peter
>
>


-- 
Cheers,
Guillaume Nodet