Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » 3.0.1 to 3.6 migration issues
3.0.1 to 3.6 migration issues [message #1229013] Wed, 08 January 2014 14:42 Go to next message
Jacob Hameiri is currently offline Jacob HameiriFriend
Messages: 43
Registered: December 2010
Member
Hi,
I am trying to update to virgo 3.6 from 3.0.1 and I am facing a problem I cant fix.

when trying to deploy my activemq bundle I get this exception :

[2014-01-08 16:19:37.354] region-dm-5                 				<> Recording application context construction failure 'org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://activemq.apache.org/schema/core]
Offending resource: URL [bundleentry://186.fwk1230588552/META-INF/spring/activemq-broker.xml]
' for bundle 'nsdop.amq_2.5.3.1 [186]' 
[2014-01-08 16:19:37.360] region-dm-5                 				<AG0000E> Application context creation failure for bundle 'nsdop.amq' version '2.5.3.1'. org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://activemq.apache.org/schema/core]
Offending resource: URL [bundleentry://186.fwk1230588552/META-INF/spring/activemq-broker.xml]

	at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
	at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
	at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:80)
	at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:316)
	at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1416)
	at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1409)
	at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:184)
	at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:140)
	at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:111)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209)
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:180)
	at org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:170)
	at org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:140)
	at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:131)
	at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:522)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$800(AbstractDelegatedExecutionApplicationContext.java:60)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$3.run(AbstractDelegatedExecutionApplicationContext.java:242)
	at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.startRefresh(AbstractDelegatedExecutionApplicationContext.java:220)
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:224)
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:177)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:157)
	at org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager$1.run(LifecycleManager.java:211)
	at org.eclipse.virgo.kernel.agent.dm.ContextPropagatingTaskExecutor$2.run(ContextPropagatingTaskExecutor.java:95)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)


is it because of the move to blueprint ? I think activemq depends on spring dm

Report message to a moderator

Re: 3.0.1 to 3.6 migration issues [message #1229352 is a reply to message #1229013] Thu, 09 January 2014 09:02 Go to previous messageGo to next message
Florian Waibel is currently offline Florian WaibelFriend
Messages: 166
Registered: June 2010
Senior Member
Hi,

I don't know very much about ActiveMQ and do not have a working example at hand. Could you provide a minimal working example for Virgo 3.0.1?

Regards,
florian

Report message to a moderator

Re: 3.0.1 to 3.6 migration issues [message #1229404 is a reply to message #1229352] Thu, 09 January 2014 11:27 Go to previous messageGo to next message
Jacob Hameiri is currently offline Jacob HameiriFriend
Messages: 43
Registered: December 2010
Member
I think I stumbled into a known ActiveMQ osgi issue that is solved in a newer ActiveMQ version, but now with ActiveMQ 5.9 I am facing what I think is an aries - gemini conflict :


[2014-01-08 23:06:30.743]  TCP Connection(6)-127.0.0.1				<DE0002E> Installation of bundle 'nsdop.amq' version '2.5.3.1' failed. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'nsdop.amq' at version '2.5.3.1': Cannot resolve: nsdop.amq
    Resolver report:
        An Import-Package could not be resolved. Resolver error data <Import-Package: org.apache.activemq.openwire.v1; version="0.0.0">. Caused by missing constraint in bundle <nsdop.amq_2.5.3.1>
             constraint: <Import-Package: org.apache.activemq.openwire.v1; version="0.0.0"> constrained to bundle <org.apache.activemq.activemq-osgi> constrained bundle version range "[5.9.0,5.9.0]"
        An Import-Package could not be resolved. Resolver error data <Import-Package: org.iq80.leveldb; version="0.0.0">. Caused by missing constraint in bundle <org.fusesource.leveldbjni_1.7.0>
             constraint: <Import-Package: org.iq80.leveldb; version="0.0.0">
        An Import-Package could not be resolved. Resolver error data <Import-Package: org.osgi.service.blueprint; version="[1.0.0,2.0.0)">. Caused by missing constraint in bundle <org.apache.activemq.activemq-osgi_5.9.0>
             constraint: <Import-Package: org.osgi.service.blueprint; version="[1.0.0,2.0.0)">



seems that ActiveMQ osgi bundle requires org.osgi.service.blueprint which is not exported by gemini 1.0.2 , is there any known workaround ?

Report message to a moderator

Re: 3.0.1 to 3.6 migration issues [message #1229518 is a reply to message #1229404] Thu, 09 January 2014 16:07 Go to previous messageGo to next message
Florian Waibel is currently offline Florian WaibelFriend
Messages: 166
Registered: June 2010
Senior Member
Missing name Mising name wrote on Thu, 09 January 2014 06:27
seems that ActiveMQ osgi bundle requires org.osgi.service.blueprint which is not exported by gemini 1.0.2 , is there any known workaround ?


You are right. This is fixed with Bug 351755 in 2.0.0.M01.

You could add the missing export via fragment. See Glyn blog post.

Report message to a moderator

Re: 3.0.1 to 3.6 migration issues [message #1231470 is a reply to message #1229518] Tue, 14 January 2014 19:04 Go to previous message
Jacob Hameiri is currently offline Jacob HameiriFriend
Messages: 43
Registered: December 2010
Member
thanks, I ended up embedding all the activemq dependencies in my bundle

Report message to a moderator

Previous Topic:Par/plan Scoping issue
Next Topic:more 3.6 update issues
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Apr 19 09:09:03 GMT 2024

Powered by FUDForum. Page generated in 0.02277 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly