You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Aliosha79 <al...@yahoo.it> on 2011/12/21 14:38:23 UTC
ServiceMix - Camel - JMS deployment error
Hi, i'm new in this forum. I hope to get your help.
I'm trying to follow this tutorial:
http://servicemix.apache.org/33-adding-a-jms-su.html
I wrote all the code lited in the previous pages, buildin succesfully the
camel-jms component having this bean.xml:
/<beans xmlns:jms="http://servicemix.apache.org/jms/1.0"
xmlns:tutorial="urn:org:apache:servicemix:tutorial:camel"
xmlns:amq="http://activemq.org/config/1.0">
<jms:provider service="tutorial:jms"
endpoint="provider"
destinationName="tutorial.camel.queue"
connectionFactory="#connectionFactory" />
<jms:consumer service="tutorial:jms"
endpoint="consumer"
destinationName="tutorial.camel.queue"
connectionFactory="#connectionFactory"
targetService="tutorial:jms"
targetEndpoint="consumer" />
<amq:connectionFactory id="connectionFactory"
brokerURL="tcp://localhost:61616" />
</beans>
But when i deploy the service assembly into the servicemix deploy folder i
get this error in the logout:
12:52:39,064 | WARN | rint Extender: 2 | FileSystemXmlApplicationContext |
61 - org.springframework.context - 3.0.5.RELEASE | Exception thrown from
ApplicationListener handling ContextClosedEvent
java.lang.IllegalStateException: ApplicationEventMulticaster not initialized
- call 'refresh' before multicasting events via the context:
org.apache.xbean.spring.context.FileSystemXmlApplicationContext@35cc4a32:
startup date [Wed Dec 21 12:52:38 CET 2011]; root of context hierarchy
at
org.springframework.context.support.AbstractApplicationContext.getApplicationEventMulticaster(AbstractApplicationContext.java:316)[61:org.springframework.context:3.0.5.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:303)[61:org.springframework.context:3.0.5.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:1007)[61:org.springframework.context:3.0.5.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:970)[61:org.springframework.context:3.0.5.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.destroy(AbstractApplicationContext.java:958)[61:org.springframework.context:3.0.5.RELEASE]
at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:107)[121:servicemix-common:2011.01.0]
at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)[121:servicemix-common:2011.01.0]
at
org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)[121:servicemix-common:2011.01.0]
at
org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:104)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:207)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.deployer.impl.Deployer.checkPendingInstallers(Deployer.java:558)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.deployer.impl.Deployer.lifeCycleChanged(Deployer.java:608)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.deployer.artifacts.AbstractLifecycleJbiArtifact.fireEvent(AbstractLifecycleJbiArtifact.java:102)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.deployer.artifacts.AbstractLifecycleJbiArtifact.fireEvent(AbstractLifecycleJbiArtifact.java:92)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.deployer.artifacts.ComponentImpl$ComponentWrapper.init(ComponentImpl.java:250)[124:org.apache.servicemix.jbi.deployer:1.4.0]
at
org.apache.servicemix.jbi.runtime.impl.ComponentRegistryImpl.doRegister(ComponentRegistryImpl.java:89)[122:org.apache.servicemix.jbi.runtime:1.4.0]
at
org.apache.servicemix.jbi.runtime.impl.ComponentRegistryImpl.doRegister(ComponentRegistryImpl.java:38)[122:org.apache.servicemix.jbi.runtime:1.4.0]
at
org.apache.servicemix.nmr.core.ServiceRegistryImpl.register(ServiceRegistryImpl.java:47)[83:org.apache.servicemix.nmr.core:1.4.0]
at
org.apache.servicemix.nmr.osgi.OsgiServiceRegistryTracker.addingService(OsgiServiceRegistryTracker.java:78)[84:org.apache.servicemix.nmr.osgi:1.4.0]
at
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896)[karaf.jar:]
at
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261)[karaf.jar:]
I'm getting mad to undertand the error. I'm using ServiceMix 4.3.0 and the
embedded Camel version is the 2.6.0 ... while the spring framework is the
3.0.5. Could someone explain me what is going on with this jbi component?
Thanks a lot.
--
View this message in context: http://camel.465427.n5.nabble.com/ServiceMix-Camel-JMS-deployment-error-tp5091937p5091937.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: ServiceMix - Camel - JMS deployment error
Posted by Aliosha79 <al...@yahoo.it>.
Thanks for the answer...
My use case brings me to mix servicemix & camel, as you can see in the link
i posted in the previous post. I really don't know the reason of this issue
but, sealing the net, i catched some post telling that, perhaps, it could be
matter of camel version embedded in servicemix.
So i decided to post this issue here too. Maybe you're right, and i have
already posted the same issue on the servicemix forum... hoping someone
could help me.
Thanks.
Alessio
--
View this message in context: http://camel.465427.n5.nabble.com/ServiceMix-Camel-JMS-deployment-error-tp5091937p5092313.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: ServiceMix - Camel - JMS deployment error
Posted by bvahdat <ba...@swissonline.ch>.
Hi Aliosha,
I assume you're in the wrong forum and should better make use of [1] to
solve your problem as
you make use of ServiceMix ESB & JBI-Container as such and the issue you're
encountering has
nothing to do with Apache Camel. Maybe [2] can also better clarify the
comparision between
ServiceMix & Camel to you. And in the case of Camel you would make use of
[3] to define your JMS
routing logic.
But who knows, maybe I'm indeed wrong!
[1] http://servicemix.apache.org/discussion-forums.html
[2] http://camel.apache.org/how-does-camel-compare-to-servicemix.html
[3] http://camel.apache.org/jms
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/ServiceMix-Camel-JMS-deployment-error-tp5091937p5092158.html
Sent from the Camel Development mailing list archive at Nabble.com.