You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Krzysztof Sobkowiak <kr...@gmail.com> on 2016/08/24 23:58:30 UTC
Re: ActiveMQ and Camel 2.17.x on Karaf
Hi
I have just tried ActiveMQ 5.14.0 with Camel 2.17.3 on Karaf 4.0.6
karaf@root()> feature:repo-add camel 2.17.3
Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
karaf@root()> feature:repo-add activemq 5.14.0
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.0/xml/features
karaf@root()> feature:install activemq-broker-noweb
karaf@root()> activemq:list
brokerName = amq-broker
karaf@root()> feature:install activemq-camel
karaf@root()> activemq:list
brokerName = amq-broker
karaf@root()> dstat
Name Queue Size Producer # Consumer # Enqueue # Dequeue # Forward # Memory %
ActiveMQ.Advisory.MasterBroker 0 0 0 1 0 0 0
karaf@root()>
No more problems while installing all the components (like before). But after restart following exception can be found in logs and the broker is down
...
Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [61]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)[:1.7.0_80]
at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)[134:org.apache.servicemix.bundles.spring-core:4.2.5.RELEASE_1]
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:125)[131:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1]
... 26 more
The bundle exporting the missing class is installed in Karaf
karaf@root()> exports | grep org.apache.xbean.spring.context
org.apache.xbean.spring.context.impl | 3.18.0 | 88 | org.apache.xbean.spring
org.apache.xbean.spring.context.v2 | 3.18.0 | 88 | org.apache.xbean.spring
org.apache.xbean.spring.context.v2c | 3.18.0 | 88 | org.apache.xbean.spring
org.apache.xbean.spring.context | 3.18.0 | 88 | org.apache.xbean.spring
The activemq-osgi bundle has enabled dynamic import, but only following xbean packages are imported
karaf@root()> headers 61
..........
DynamicImport-Package =
*
.........
org.apache.xbean.spring.context;resolution:=optional;version="[3.13,5)",
org.apache.xbean.spring.context.impl;resolution:=optional;version="[3.13,5)",
...............
It looks like the org.apache.xbean.spring.context.v2 package is not correctly resolved after restart.
Regards
Krzysztof
On 13.06.2016 08:03, Jean-Baptiste Onofr� wrote:
> Hi Krzysztof
>
> I will resume my work on it.
>
> I will keep you posted soon.
>
> Regards
> JB
>
> On 06/12/2016 09:34 PM, Krzysztof Sobkowiak wrote:
>> Hi
>>
>> Any news about this problem?
>>
>> Regards
>> Krzysztof
>>
>> On 28.04.2016 21:21, Krzysztof Sobkowiak wrote:
>>> It looks like it's again the problem with installing of multiple Spring versions while ActiveMQ bundles are already present in Karaf. Spring 3.2.14.RELEASE_1 was already installed with the broker and now all other Spring versions are installed with activemq-camel feature.
>>>
>>> karaf@root()> feature:install -v activemq-camel
>>> Adding features: activemq-camel/[5.13.3,5.13.3]
>>> Changes to perform:
>>> Region: root
>>> Bundles to update:
>>> org.apache.servicemix.bundles.jaxb-impl/2.2.11.1 with mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jaxb-impl/2.2.6_1
>>> Bundles to install:
>>> mvn:org.apache.activemq/activemq-camel/5.13.3
>>> mvn:org.apache.camel/camel-blueprint/2.17.0
>>> mvn:org.apache.camel/camel-catalog/2.17.0
>>> mvn:org.apache.camel/camel-commands-core/2.17.0
>>> mvn:org.apache.camel/camel-core/2.17.0
>>> mvn:org.apache.camel/camel-jms/2.17.0
>>> mvn:org.apache.camel.karaf/camel-karaf-commands/2.17.0
>>> mvn:commons-codec/commons-codec/1.9
>>> mvn:commons-pool/commons-pool/1.6
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/4.2.5.RELEASE_1
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/4.2.5.RELEASE_1
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/4.2.5.RELEASE_1
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/4.2.5.RELEASE_1
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/4.2.5.RELEASE_1
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/4.2.5.RELEASE_1
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-jms/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-jms/4.2.5.RELEASE_1
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-tx/4.1.7.RELEASE_2
>>> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-tx/4.2.5.RELEASE_1
>>> mvn:org.springframework/spring-aop/3.1.4.RELEASE
>>> mvn:org.springframework/spring-asm/3.1.4.RELEASE
>>> mvn:org.springframework/spring-beans/3.1.4.RELEASE
>>> mvn:org.springframework/spring-context/3.1.4.RELEASE
>>> mvn:org.springframework/spring-context-support/3.1.4.RELEASE
>>> mvn:org.springframework/spring-core/3.1.4.RELEASE
>>> mvn:org.springframework/spring-expression/3.1.4.RELEASE
>>> mvn:org.codehaus.woodstox/stax2-api/3.1.4
>>> mvn:org.codehaus.woodstox/woodstox-core-asl/4.4.1
>>> .......
>>>
>>> I have described something similar here http://karaf.922171.n3.nabble.com/Feature-spring-4-2-3-RELEASE-1-also-installs-bundles-from-Spring-version-3-1-4-when-activemq-is-instd-td4046213.html.
>>>
>>> Regards
>>> Krzysztof
>>>
>>>
>>>
>>> On 28.04.2016 00:27, Krzysztof Sobkowiak wrote:
>>>> Hi
>>>>
>>>> I have tried to install activemq-broker-noweb and activemq-camel features (5.13.2, 5.13.3 and current master) with Camel 2.17.0 on Karaf 4.0.5 but with no success:
>>>>
>>>> karaf@root()> feature:repo-add camel 2.17.0
>>>> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.0/xml/features
>>>> karaf@root()> feature:repo-add activemq 5.13.2
>>>> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.13.2/xml/features
>>>> karaf@root()> feature:install activemq-broker-noweb
>>>> karaf@root()> activemq:list
>>>> brokerName = amq-broker
>>>>
>>>> karaf@root()> feature:install activemq-camel
>>>> karaf@root()> activemq:list
>>>> karaf@root()>
>>>>
>>>> The activemq-osgi bundle is refreshed and and cannot be resolved anymore
>>>>
>>>> There is following entry in log
>>>>
>>>> Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [61]
>>>> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)[:1.7.0_80]
>>>> at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1925)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.apache.felix.framework.BundleImpl.loadClass(BundleImpl.java:978)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.springframework.osgi.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:99)[124:org.springframework.osgi.core:1.2.1]
>>>> ... 36 more
>>>>
>>>> There is a bundle providing this package
>>>>
>>>> karaf@root()> exports | grep org.apache.xbean.spring.context.v2
>>>> org.apache.xbean.spring.context.v2 | 3.18.0 | 91 | org.apache.xbean.spring
>>>> org.apache.xbean.spring.context.v2c | 3.18.0 | 91 | org.apache.xbean.spring
>>>>
>>>> It looks like activemq-osgi doesn't import this package. But setting dynamic-imports on it causes further error
>>>>
>>>> Caused by: java.lang.ClassNotFoundException: org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext not found by org.apache.activemq.activemq-osgi [61]
>>>> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)
>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)[:1.7.0_80]
>>>> ... 46 more
>>>>
>>>> There is a bundle providing this package available
>>>>
>>>> karaf@root()> exports | grep org.springframework.osgi.context.support
>>>> org.springframework.osgi.context.support | 1.2.1 | 124 | org.springframework.osgi.core
>>>>
>>>> One another interesting thing - headers command on activemq-osgi shows following import
>>>>
>>>> org.springframework.osgi.context.support;resolution:=optional;version="[3,5)"
>>>>
>>>> but in ActiveMQ code there is following entry
>>>>
>>>> org.springframework.osgi*;version="[1,4]";resolution:=optional
>>>>
>>>> I think, the range [3,5) is the reason why the package org.springframework.osgi.context.supportcannot be resolved, because it's provided in version 1.2.1
>>>>
>>>> Do you have any ideas why this problem happens? I think, it's something connected with the changes in Spring dependencies in Camel 2.17.0
>>>>
>>>> Regards
>>>> Krzysztof
>>
>
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by IODB <iv...@caffeinated-consulting.com>.
Indeed, the problem still occurs with ActiveMQ 5.15.0-SNAPSHOT.
Interestingly enough, it looks like the error only occurs when restarting
after camel-jms is installed.
I'd be perfectly happy using activemq blueprint, but couldn't find much
documentation about how to set it up.
Also, I've tried using camel-sjms instead of camel-jms. The broker starts up
without errors, but unfortunately camel-sjms doesn't seem to support
retrieving the destinationName from a message header (like
'CamelJmsDestinationName' in camel-jms) , which is a feature I can't live
without.
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048829.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Sorry, it should go to Karaf list
On 19.01.2017 01:16, Krzysztof Sobkowiak wrote:
> My mistake. This problem still happens in the sample steps below - the exception still occurs after Karaf restart and broker doesn't start.
> But adding camel-cxf seems to fix this problem
>
> feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel activemq-broker-noweb activemq-blueprint
>
> Kindly regards
> Krzysztof
>
>
> On 14.01.2017 22:55, Krzysztof Sobkowiak wrote:
>> Hi
>>
>> I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 (also 4.0.7):
>>
>>
>> __ __ ____
>> / //_/____ __________ _/ __/
>> / ,< / __ `/ ___/ __ `/ /_
>> / /| |/ /_/ / / / /_/ / __/
>> /_/ |_|\__,_/_/ \__,_/_/
>>
>> Apache Karaf (4.0.8)
>>
>> Hit '<tab>' for a list of available commands
>> and '[cmd] --help' for help on a specific command.
>> Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
>>
>> karaf@root()> feature:repo-add camel 2.17.3
>> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
>> karaf@root()> feature:repo-add activemq 5.14.3
>> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
>> karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel activemq-broker-noweb activemq-blueprint
>> karaf@root()> activemq:list
>> brokerName = amq-broker
>>
>>
>> Kindly tegards
>> Krzysztof
>>
>> On 30.11.2016 14:11, IODB wrote:
>>> Can somebody refer me to the relevant Jira issue, so I can track its
>>> progress?
>>>
>>> Thanks
>>>
>
> --
> Krzysztof Sobkowiak (@ksobkowiak)
>
> JEE & OSS Architect, Integration Architect
> Apache Software Foundation Member (http://apache.org/)
> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
> Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
My mistake. This problem still happens in the sample steps below - the exception still occurs after Karaf restart and broker doesn't start.
But adding camel-cxf seems to fix this problem
feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel activemq-broker-noweb activemq-blueprint
Kindly regards
Krzysztof
On 14.01.2017 22:55, Krzysztof Sobkowiak wrote:
> Hi
>
> I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 (also 4.0.7):
>
>
> __ __ ____
> / //_/____ __________ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
>
> Apache Karaf (4.0.8)
>
> Hit '<tab>' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
>
> karaf@root()> feature:repo-add camel 2.17.3
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
> karaf@root()> feature:repo-add activemq 5.14.3
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
> karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel activemq-broker-noweb activemq-blueprint
> karaf@root()> activemq:list
> brokerName = amq-broker
>
>
> Kindly tegards
> Krzysztof
>
> On 30.11.2016 14:11, IODB wrote:
>> Can somebody refer me to the relevant Jira issue, so I can track its
>> progress?
>>
>> Thanks
>>
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Embedding xbean-spring bundle into activemq-osgi solves the problem with Camel 2.17.x and 2.18.x. I have created an Issue in ActiveQM (AMQ-6576) and a pull request with the fix. Hope it will solve the problem (and make no new problems :-) ). I have tested the modified ActiveQM with ServiceMix (manually and itests) as well as a smoke test to be sure this change didn't make any new errors.
Kindly regards
Krzysztof
On 24.01.2017 00:48, Krzysztof Sobkowiak wrote:
> Hi
>
> I have performed some analysis for 2.17.5 (for 2.18.x problem looks more complicated)
>
> karaf@root()> feature:repo-add camel 2.17.5
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.5/xml/features
> karaf@root()> feature:repo-add activemq 5.14.3
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
>
> And now:
>
> karaf@root()> feature:install -v activemq-camel
> Adding features: activemq-camel/[5.14.3,5.14.3]
> Changes to perform:
> Region: root
> Bundles to install:
> .....
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/4.2.8.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/4.2.8.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/4.2.8.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/4.2.8.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/4.2.8.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/4.2.8.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-jms/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-jms/4.2.8.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-tx/3.2.17.RELEASE_1
> mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-tx/4.2.8.RELEASE_1
>
> 2 versions of Spring are installed.
>
> Now:
>
> karaf@root()> list -t 0
> START LEVEL 100 , List Threshold: 0
> ID | State | Lvl | Version | Name
> ------------------------------------------------------------------------------------------------------------
> ....
> 69 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
> 70 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
> 71 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
> 72 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
> 73 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
> 74 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
> 75 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
> 76 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
> 77 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
> 78 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
> 79 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
> 80 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
> 81 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-jms
> 82 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-jms
> 83 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-tx
> 84 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-tx
>
> And when you examine the dependency tree of activemq-camel you can see following (excuse me long listings):
>
> karaf@root()> bundle:tree-show 52
> Bundle org.apache.activemq.activemq-camel [52] is currently ACTIVE
>
> org.apache.activemq.activemq-camel [52]
> +- org.apache.servicemix.bundles.spring-core [77]
> | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.karaf.services.eventadmin [6]
> | +- org.apache.felix.configadmin [3]
> | +- org.apache.felix.metatype [5]
> +- org.apache.servicemix.bundles.spring-jms [81]
> | +- org.apache.servicemix.bundles.spring-core [77]
> | +- org.apache.servicemix.bundles.spring-beans [71]
> | | +- org.apache.servicemix.bundles.spring-core [77]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.servicemix.bundles.spring-aop [69]
> | | +- org.apache.servicemix.bundles.spring-core [77]
> | | +- org.apache.servicemix.bundles.spring-beans [71]
> | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | +- org.apache.commons.pool [61]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.servicemix.bundles.spring-context [73]
> | | +- org.apache.servicemix.bundles.spring-expression [79]
> | | | +- org.apache.servicemix.bundles.spring-core [77]
> | | +- org.apache.servicemix.bundles.spring-core [77]
> | | +- org.apache.servicemix.bundles.spring-aop [69]
> | | +- org.apache.servicemix.bundles.spring-beans [71]
> | | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | | | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
> | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | +- org.apache.servicemix.bundles.spring-tx [83]
> | | +- org.apache.servicemix.bundles.spring-core [77]
> | | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
> | | +- org.apache.servicemix.bundles.spring-beans [71]
> | | +- org.apache.servicemix.bundles.spring-aop [69]
> | | +- org.apache.servicemix.bundles.spring-context [73]
> | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.servicemix.bundles.aopalliance [67]
> | +- org.ops4j.pax.logging.pax-logging-api [1]
> +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> +- org.apache.servicemix.bundles.spring-tx [83]
> +- org.apache.activemq.activemq-osgi [53]
> | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
> | +- org.apache.commons.net [60]
> | +- org.apache.aries.blueprint.api [10]
> | +- org.apache.servicemix.bundles.spring-beans [71]
> | +- org.apache.hadoop.zookeeper [66]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.jvnet.jaxb2_commons.jaxb2-basics-runtime [86]
> | | +- org.apache.servicemix.bundles.jaxb-impl [68]
> | +- org.apache.aries.blueprint.core [12]
> | | +- org.apache.aries.proxy.api [19]
> | | | +- org.apache.aries.util [21]
> | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | +- org.apache.aries.blueprint.api [10]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | +- org.apache.aries.util [21]
> | | +- org.apache.karaf.services.eventadmin [6]
> | +- org.apache.geronimo.specs.geronimo-j2ee-management_1.1_spec [63]
> | +- org.apache.camel.camel-jms [58]
> | | +- org.apache.servicemix.bundles.spring-jms [81]
> | | +- org.apache.servicemix.bundles.spring-core [77]
> | | +- org.apache.servicemix.bundles.spring-beans [71]
> | | +- org.apache.servicemix.bundles.spring-context [73]
> | | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | | +- org.apache.servicemix.bundles.spring-tx [83]
> | | +- org.apache.camel.camel-core [57]
> | | | +- org.apache.servicemix.bundles.spring-tx [84]
> | | | | +- org.apache.servicemix.bundles.spring-aop [70]
> | | | | | +- org.apache.commons.pool2 [62]
> | | | | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | | | | +- org.apache.servicemix.bundles.spring-core [78]
> | | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | | | | +- org.apache.servicemix.bundles.spring-beans [72]
> | | | | | | +- org.apache.servicemix.bundles.spring-core [78]
> | | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | | | | +- org.apache.commons.pool [61]
> | | | | +- org.apache.servicemix.bundles.spring-context [74]
> | | | | | +- org.apache.servicemix.bundles.spring-aop [70]
> | | | | | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | | | | | +- org.apache.servicemix.bundles.spring-expression [80]
> | | | | | | +- org.apache.servicemix.bundles.spring-core [78]
> | | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | | | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | | | | +- org.apache.servicemix.bundles.spring-core [78]
> | | | | | +- org.apache.servicemix.bundles.spring-beans [72]
> | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | | | +- org.apache.servicemix.bundles.spring-core [78]
> | | | | +- org.apache.servicemix.bundles.spring-beans [72]
> | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.servicemix.bundles.spring-core [77]
> | +- org.apache.servicemix.bundles.spring-jms [81]
> | +- org.apache.servicemix.bundles.spring-aop [69]
> | +- org.apache.felix.configadmin [3]
> | +- org.apache.servicemix.bundles.spring-context [73]
> | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | +- org.apache.servicemix.bundles.spring-tx [83]
> | +- org.apache.commons.pool2 [62]
> | +- org.objectweb.asm.all [50]
> | +- org.apache.servicemix.bundles.aopalliance [67]
> | +- org.apache.camel.camel-core [57]
> | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.xbean.spring [85]
> | +- org.apache.servicemix.bundles.spring-core [77]
> | +- org.apache.servicemix.bundles.spring-beans [71]
> | +- org.apache.servicemix.bundles.spring-context [73]
> | +- org.ops4j.pax.logging.pax-logging-api [1]
> +- org.apache.camel.camel-core [57]
> +- org.ops4j.pax.logging.pax-logging-api [1]
> +- org.apache.camel.camel-jms [58]
>
>
> As you can see, almost everywhere the version 3.2.17.RELEASE_1 of Spring bundles are wired, but camel-core wires the Spring 4.2.8.RELEASE_1
>
> Of course, after restart well known exception
>
> Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [53]
>
> Let's inspect again.
>
> karaf@root()> bundle:tree-show 52
> Bundle org.apache.activemq.activemq-camel [52] is currently ACTIVE
>
> org.apache.activemq.activemq-camel [52]
> +- org.apache.servicemix.bundles.spring-tx [84]
> | +- org.apache.servicemix.bundles.spring-aop [70]
> | | +- org.apache.commons.pool2 [62]
> | | +- org.apache.commons.pool [61]
> | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | +- org.apache.servicemix.bundles.spring-beans [72]
> | | | +- org.apache.servicemix.bundles.spring-core [78]
> | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | | | +- org.apache.karaf.services.eventadmin [6]
> | | | | +- org.apache.felix.metatype [5]
> | | | | +- org.apache.felix.configadmin [3]
> | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | +- org.apache.servicemix.bundles.spring-core [78]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.servicemix.bundles.spring-context [74]
> | | +- org.apache.servicemix.bundles.spring-expression [80]
> | | | +- org.apache.servicemix.bundles.spring-core [78]
> | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | +- org.apache.servicemix.bundles.spring-aop [70]
> | | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | | | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
> | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | +- org.apache.servicemix.bundles.spring-beans [72]
> | | +- org.apache.servicemix.bundles.spring-core [78]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.servicemix.bundles.aopalliance [67]
> | +- org.apache.servicemix.bundles.spring-beans [72]
> | +- org.apache.servicemix.bundles.spring-core [78]
> | +- org.ops4j.pax.logging.pax-logging-api [1]
> +- org.apache.activemq.activemq-osgi [53]
> | +- org.apache.commons.pool2 [62]
> | +- org.apache.geronimo.specs.geronimo-j2ee-management_1.1_spec [63]
> | +- org.apache.felix.configadmin [3]
> | +- org.apache.hadoop.zookeeper [66]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.aries.blueprint.core [12]
> | | +- org.apache.karaf.services.eventadmin [6]
> | | +- org.apache.aries.blueprint.api [10]
> | | +- org.apache.aries.proxy.api [19]
> | | | +- org.apache.aries.util [21]
> | | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | | +- org.apache.aries.util [21]
> | +- org.apache.commons.net [60]
> | +- org.apache.servicemix.bundles.spring-context [74]
> | +- org.apache.camel.camel-core [57]
> | | +- org.apache.servicemix.bundles.spring-tx [84]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.apache.servicemix.bundles.spring-core [78]
> | +- org.apache.servicemix.bundles.spring-tx [84]
> | +- org.apache.servicemix.bundles.spring-aop [70]
> | +- org.apache.servicemix.bundles.spring-jms [82]
> | | +- org.apache.servicemix.bundles.spring-expression [80]
> | | +- org.apache.servicemix.bundles.spring-tx [84]
> | | +- org.apache.servicemix.bundles.spring-aop [70]
> | | +- org.apache.servicemix.bundles.spring-context [74]
> | | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | | +- org.apache.servicemix.bundles.aopalliance [67]
> | | +- org.apache.servicemix.bundles.spring-beans [72]
> | | +- org.apache.servicemix.bundles.spring-core [78]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.jvnet.jaxb2_commons.jaxb2-basics-runtime [86]
> | | +- org.apache.servicemix.bundles.jaxb-impl [68]
> | +- org.apache.aries.blueprint.api [10]
> | +- org.objectweb.asm.all [50]
> | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | +- org.apache.servicemix.bundles.aopalliance [67]
> | +- org.apache.servicemix.bundles.spring-beans [72]
> | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
> | +- org.apache.camel.camel-jms [58]
> | | +- org.apache.servicemix.bundles.spring-tx [84]
> | | +- org.apache.servicemix.bundles.spring-jms [82]
> | | +- org.apache.servicemix.bundles.spring-context [74]
> | | +- org.apache.camel.camel-core [57]
> | | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> | | +- org.apache.servicemix.bundles.spring-beans [72]
> | | +- org.apache.servicemix.bundles.spring-core [78]
> | | +- org.ops4j.pax.logging.pax-logging-api [1]
> | +- org.ops4j.pax.logging.pax-logging-api [1]
> +- org.apache.servicemix.bundles.spring-jms [82]
> +- org.apache.camel.camel-core [57]
> +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
> +- org.apache.servicemix.bundles.spring-core [78]
> +- org.apache.camel.camel-jms [58]
> +- org.ops4j.pax.logging.pax-logging-api [1]
>
> Now all bundles are re-wired and you can see all bundles use the Spring 4.2.8.RELEASE_1, but there is no org.apache.xbean.spring in this dependency tree. Probably because of the error while restarting Karaf. When we inspect this bundle we can see it doesn't allow to wire the Spring 4.
>
> org.springframework.beans;version="[2.5,4)",
> org.springframework.beans.factory;version="[2.5,4)",
> org.springframework.beans.factory.config;version="[2.5,4)",
> org.springframework.beans.factory.parsing;version="[2.5,4)",
> org.springframework.beans.factory.support;version="[2.5,4)",
> org.springframework.beans.factory.xml;version="[2.5,4)",
> org.springframework.context;version="[2.5,4)",
> org.springframework.context.support;version="[2.5,4)",
> org.springframework.core.io;version="[2.5,4)",
> org.springframework.core.io.support;version="[2.5,4)",
> org.springframework.util;version="[2.5,4)",
> org.springframework.util.xml;version="[2.5,4)",
>
> So we have one bundle which cannot use the same Spring version like all other bundles. Maybe this is the problem.
>
> Kindly regards
> Krzysztof
>
>
>
> On 19.01.2017 08:15, Sobkowiak Krzysztof wrote:
>> Btw, this trick with camel-cxf doesn't help with Camel 2.18.x. I think, there was a change in Camel 2.17.3 which helped with this problem (but not completely yet), but the change is not available in 2.18.x (I tried current snapshot and it didn't help too).
>>
>> It looks like this change has helped in 2.17.3 https://github.com/apache/camel/commit/284cc6780de1e32468ef2ae50ad357a444e79da1 (CAMEL-10153), which introduces [3.2,5) as version range for spring in camel-cxf. In 2.18.x there is still used the version range [4.1,5)
>>
>> Regards
>> Krzysztof
>>
>> On 19.01.2017 01:17, Krzysztof Sobkowiak wrote:
>>> My mistake. This problem still happens in the sample steps below - the exception still occurs after Karaf restart and broker doesn't start.
>>> But adding camel-cxf seems to fix this problem
>>>
>>> feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel activemq-broker-noweb activemq-blueprint
>>>
>>> Kindly regards
>>> Krzysztof
>>>
>>>
>>> On 14.01.2017 22:55, Krzysztof Sobkowiak wrote:
>>>> Hi
>>>>
>>>> I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 (also 4.0.7):
>>>>
>>>>
>>>> __ __ ____
>>>> / //_/____ __________ _/ __/
>>>> / ,< / __ `/ ___/ __ `/ /_
>>>> / /| |/ /_/ / / / /_/ / __/
>>>> /_/ |_|\__,_/_/ \__,_/_/
>>>>
>>>> Apache Karaf (4.0.8)
>>>>
>>>> Hit '<tab>' for a list of available commands
>>>> and '[cmd] --help' for help on a specific command.
>>>> Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
>>>>
>>>> karaf@root()> feature:repo-add camel 2.17.3
>>>> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
>>>> karaf@root()> feature:repo-add activemq 5.14.3
>>>> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
>>>> karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel activemq-broker-noweb activemq-blueprint
>>>> karaf@root()> activemq:list
>>>> brokerName = amq-broker
>>>>
>>>>
>>>> Kindly tegards
>>>> Krzysztof
>>>>
>>>> On 30.11.2016 14:11, IODB wrote:
>>>>> Can somebody refer me to the relevant Jira issue, so I can track its
>>>>> progress?
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>> Krzysztof Sobkowiak
>>
>> JEE & OSS Architect, Integration Architect
>> Apache Software Foundation Member (http://apache.org/)
>> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
>> Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
>
>
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Hi
I have performed some analysis for 2.17.5 (for 2.18.x problem looks more complicated)
karaf@root()> feature:repo-add camel 2.17.5
Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.5/xml/features
karaf@root()> feature:repo-add activemq 5.14.3
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
And now:
karaf@root()> feature:install -v activemq-camel
Adding features: activemq-camel/[5.14.3,5.14.3]
Changes to perform:
Region: root
Bundles to install:
.....
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-aop/4.2.8.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-beans/4.2.8.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context/4.2.8.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-context-support/4.2.8.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-core/4.2.8.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-expression/4.2.8.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-jms/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-jms/4.2.8.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-tx/3.2.17.RELEASE_1
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-tx/4.2.8.RELEASE_1
2 versions of Spring are installed.
Now:
karaf@root()> list -t 0
START LEVEL 100 , List Threshold: 0
ID | State | Lvl | Version | Name
------------------------------------------------------------------------------------------------------------
....
69 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
70 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
71 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
72 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
73 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
74 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
75 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
76 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
77 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
78 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
79 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
80 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
81 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-jms
82 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-jms
83 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-tx
84 | Active | 30 | 4.2.8.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-tx
And when you examine the dependency tree of activemq-camel you can see following (excuse me long listings):
karaf@root()> bundle:tree-show 52
Bundle org.apache.activemq.activemq-camel [52] is currently ACTIVE
org.apache.activemq.activemq-camel [52]
+- org.apache.servicemix.bundles.spring-core [77]
| +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.karaf.services.eventadmin [6]
| +- org.apache.felix.configadmin [3]
| +- org.apache.felix.metatype [5]
+- org.apache.servicemix.bundles.spring-jms [81]
| +- org.apache.servicemix.bundles.spring-core [77]
| +- org.apache.servicemix.bundles.spring-beans [71]
| | +- org.apache.servicemix.bundles.spring-core [77]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.servicemix.bundles.spring-aop [69]
| | +- org.apache.servicemix.bundles.spring-core [77]
| | +- org.apache.servicemix.bundles.spring-beans [71]
| | +- org.apache.servicemix.bundles.aopalliance [67]
| | +- org.apache.commons.pool [61]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.servicemix.bundles.spring-context [73]
| | +- org.apache.servicemix.bundles.spring-expression [79]
| | | +- org.apache.servicemix.bundles.spring-core [77]
| | +- org.apache.servicemix.bundles.spring-core [77]
| | +- org.apache.servicemix.bundles.spring-aop [69]
| | +- org.apache.servicemix.bundles.spring-beans [71]
| | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| | | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
| | +- org.apache.servicemix.bundles.aopalliance [67]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| +- org.apache.servicemix.bundles.spring-tx [83]
| | +- org.apache.servicemix.bundles.spring-core [77]
| | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
| | +- org.apache.servicemix.bundles.spring-beans [71]
| | +- org.apache.servicemix.bundles.spring-aop [69]
| | +- org.apache.servicemix.bundles.spring-context [73]
| | +- org.apache.servicemix.bundles.aopalliance [67]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.servicemix.bundles.aopalliance [67]
| +- org.ops4j.pax.logging.pax-logging-api [1]
+- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
+- org.apache.servicemix.bundles.spring-tx [83]
+- org.apache.activemq.activemq-osgi [53]
| +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
| +- org.apache.commons.net [60]
| +- org.apache.aries.blueprint.api [10]
| +- org.apache.servicemix.bundles.spring-beans [71]
| +- org.apache.hadoop.zookeeper [66]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.jvnet.jaxb2_commons.jaxb2-basics-runtime [86]
| | +- org.apache.servicemix.bundles.jaxb-impl [68]
| +- org.apache.aries.blueprint.core [12]
| | +- org.apache.aries.proxy.api [19]
| | | +- org.apache.aries.util [21]
| | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | +- org.apache.aries.blueprint.api [10]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| | +- org.apache.aries.util [21]
| | +- org.apache.karaf.services.eventadmin [6]
| +- org.apache.geronimo.specs.geronimo-j2ee-management_1.1_spec [63]
| +- org.apache.camel.camel-jms [58]
| | +- org.apache.servicemix.bundles.spring-jms [81]
| | +- org.apache.servicemix.bundles.spring-core [77]
| | +- org.apache.servicemix.bundles.spring-beans [71]
| | +- org.apache.servicemix.bundles.spring-context [73]
| | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| | +- org.apache.servicemix.bundles.spring-tx [83]
| | +- org.apache.camel.camel-core [57]
| | | +- org.apache.servicemix.bundles.spring-tx [84]
| | | | +- org.apache.servicemix.bundles.spring-aop [70]
| | | | | +- org.apache.commons.pool2 [62]
| | | | | +- org.apache.servicemix.bundles.aopalliance [67]
| | | | | +- org.apache.servicemix.bundles.spring-core [78]
| | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | | | | +- org.apache.servicemix.bundles.spring-beans [72]
| | | | | | +- org.apache.servicemix.bundles.spring-core [78]
| | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | | | | +- org.apache.commons.pool [61]
| | | | +- org.apache.servicemix.bundles.spring-context [74]
| | | | | +- org.apache.servicemix.bundles.spring-aop [70]
| | | | | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| | | | | +- org.apache.servicemix.bundles.spring-expression [80]
| | | | | | +- org.apache.servicemix.bundles.spring-core [78]
| | | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | | | | +- org.apache.servicemix.bundles.aopalliance [67]
| | | | | +- org.apache.servicemix.bundles.spring-core [78]
| | | | | +- org.apache.servicemix.bundles.spring-beans [72]
| | | | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | | | +- org.apache.servicemix.bundles.aopalliance [67]
| | | | +- org.apache.servicemix.bundles.spring-core [78]
| | | | +- org.apache.servicemix.bundles.spring-beans [72]
| | | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.servicemix.bundles.spring-core [77]
| +- org.apache.servicemix.bundles.spring-jms [81]
| +- org.apache.servicemix.bundles.spring-aop [69]
| +- org.apache.felix.configadmin [3]
| +- org.apache.servicemix.bundles.spring-context [73]
| +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| +- org.apache.servicemix.bundles.spring-tx [83]
| +- org.apache.commons.pool2 [62]
| +- org.objectweb.asm.all [50]
| +- org.apache.servicemix.bundles.aopalliance [67]
| +- org.apache.camel.camel-core [57]
| +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.xbean.spring [85]
| +- org.apache.servicemix.bundles.spring-core [77]
| +- org.apache.servicemix.bundles.spring-beans [71]
| +- org.apache.servicemix.bundles.spring-context [73]
| +- org.ops4j.pax.logging.pax-logging-api [1]
+- org.apache.camel.camel-core [57]
+- org.ops4j.pax.logging.pax-logging-api [1]
+- org.apache.camel.camel-jms [58]
As you can see, almost everywhere the version 3.2.17.RELEASE_1 of Spring bundles are wired, but camel-core wires the Spring 4.2.8.RELEASE_1
Of course, after restart well known exception
Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [53]
Let's inspect again.
karaf@root()> bundle:tree-show 52
Bundle org.apache.activemq.activemq-camel [52] is currently ACTIVE
org.apache.activemq.activemq-camel [52]
+- org.apache.servicemix.bundles.spring-tx [84]
| +- org.apache.servicemix.bundles.spring-aop [70]
| | +- org.apache.commons.pool2 [62]
| | +- org.apache.commons.pool [61]
| | +- org.apache.servicemix.bundles.aopalliance [67]
| | +- org.apache.servicemix.bundles.spring-beans [72]
| | | +- org.apache.servicemix.bundles.spring-core [78]
| | | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | | | +- org.apache.karaf.services.eventadmin [6]
| | | | +- org.apache.felix.metatype [5]
| | | | +- org.apache.felix.configadmin [3]
| | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | +- org.apache.servicemix.bundles.spring-core [78]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.servicemix.bundles.spring-context [74]
| | +- org.apache.servicemix.bundles.spring-expression [80]
| | | +- org.apache.servicemix.bundles.spring-core [78]
| | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | +- org.apache.servicemix.bundles.spring-aop [70]
| | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| | | +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
| | +- org.apache.servicemix.bundles.aopalliance [67]
| | +- org.apache.servicemix.bundles.spring-beans [72]
| | +- org.apache.servicemix.bundles.spring-core [78]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.servicemix.bundles.aopalliance [67]
| +- org.apache.servicemix.bundles.spring-beans [72]
| +- org.apache.servicemix.bundles.spring-core [78]
| +- org.ops4j.pax.logging.pax-logging-api [1]
+- org.apache.activemq.activemq-osgi [53]
| +- org.apache.commons.pool2 [62]
| +- org.apache.geronimo.specs.geronimo-j2ee-management_1.1_spec [63]
| +- org.apache.felix.configadmin [3]
| +- org.apache.hadoop.zookeeper [66]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.aries.blueprint.core [12]
| | +- org.apache.karaf.services.eventadmin [6]
| | +- org.apache.aries.blueprint.api [10]
| | +- org.apache.aries.proxy.api [19]
| | | +- org.apache.aries.util [21]
| | | +- org.ops4j.pax.logging.pax-logging-api [1]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| | +- org.apache.aries.util [21]
| +- org.apache.commons.net [60]
| +- org.apache.servicemix.bundles.spring-context [74]
| +- org.apache.camel.camel-core [57]
| | +- org.apache.servicemix.bundles.spring-tx [84]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.apache.servicemix.bundles.spring-core [78]
| +- org.apache.servicemix.bundles.spring-tx [84]
| +- org.apache.servicemix.bundles.spring-aop [70]
| +- org.apache.servicemix.bundles.spring-jms [82]
| | +- org.apache.servicemix.bundles.spring-expression [80]
| | +- org.apache.servicemix.bundles.spring-tx [84]
| | +- org.apache.servicemix.bundles.spring-aop [70]
| | +- org.apache.servicemix.bundles.spring-context [74]
| | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| | +- org.apache.servicemix.bundles.aopalliance [67]
| | +- org.apache.servicemix.bundles.spring-beans [72]
| | +- org.apache.servicemix.bundles.spring-core [78]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.jvnet.jaxb2_commons.jaxb2-basics-runtime [86]
| | +- org.apache.servicemix.bundles.jaxb-impl [68]
| +- org.apache.aries.blueprint.api [10]
| +- org.objectweb.asm.all [50]
| +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| +- org.apache.servicemix.bundles.aopalliance [67]
| +- org.apache.servicemix.bundles.spring-beans [72]
| +- org.apache.geronimo.specs.geronimo-jta_1.1_spec [65]
| +- org.apache.camel.camel-jms [58]
| | +- org.apache.servicemix.bundles.spring-tx [84]
| | +- org.apache.servicemix.bundles.spring-jms [82]
| | +- org.apache.servicemix.bundles.spring-context [74]
| | +- org.apache.camel.camel-core [57]
| | +- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
| | +- org.apache.servicemix.bundles.spring-beans [72]
| | +- org.apache.servicemix.bundles.spring-core [78]
| | +- org.ops4j.pax.logging.pax-logging-api [1]
| +- org.ops4j.pax.logging.pax-logging-api [1]
+- org.apache.servicemix.bundles.spring-jms [82]
+- org.apache.camel.camel-core [57]
+- org.apache.geronimo.specs.geronimo-jms_1.1_spec [64]
+- org.apache.servicemix.bundles.spring-core [78]
+- org.apache.camel.camel-jms [58]
+- org.ops4j.pax.logging.pax-logging-api [1]
Now all bundles are re-wired and you can see all bundles use the Spring 4.2.8.RELEASE_1, but there is no org.apache.xbean.spring in this dependency tree. Probably because of the error while restarting Karaf. When we inspect this bundle we can see it doesn't allow to wire the Spring 4.
org.springframework.beans;version="[2.5,4)",
org.springframework.beans.factory;version="[2.5,4)",
org.springframework.beans.factory.config;version="[2.5,4)",
org.springframework.beans.factory.parsing;version="[2.5,4)",
org.springframework.beans.factory.support;version="[2.5,4)",
org.springframework.beans.factory.xml;version="[2.5,4)",
org.springframework.context;version="[2.5,4)",
org.springframework.context.support;version="[2.5,4)",
org.springframework.core.io;version="[2.5,4)",
org.springframework.core.io.support;version="[2.5,4)",
org.springframework.util;version="[2.5,4)",
org.springframework.util.xml;version="[2.5,4)",
So we have one bundle which cannot use the same Spring version like all other bundles. Maybe this is the problem.
Kindly regards
Krzysztof
On 19.01.2017 08:15, Sobkowiak Krzysztof wrote:
> Btw, this trick with camel-cxf doesn't help with Camel 2.18.x. I think, there was a change in Camel 2.17.3 which helped with this problem (but not completely yet), but the change is not available in 2.18.x (I tried current snapshot and it didn't help too).
>
> It looks like this change has helped in 2.17.3 https://github.com/apache/camel/commit/284cc6780de1e32468ef2ae50ad357a444e79da1 (CAMEL-10153), which introduces [3.2,5) as version range for spring in camel-cxf. In 2.18.x there is still used the version range [4.1,5)
>
> Regards
> Krzysztof
>
> On 19.01.2017 01:17, Krzysztof Sobkowiak wrote:
>> My mistake. This problem still happens in the sample steps below - the exception still occurs after Karaf restart and broker doesn't start.
>> But adding camel-cxf seems to fix this problem
>>
>> feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel activemq-broker-noweb activemq-blueprint
>>
>> Kindly regards
>> Krzysztof
>>
>>
>> On 14.01.2017 22:55, Krzysztof Sobkowiak wrote:
>>> Hi
>>>
>>> I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 (also 4.0.7):
>>>
>>>
>>> __ __ ____
>>> / //_/____ __________ _/ __/
>>> / ,< / __ `/ ___/ __ `/ /_
>>> / /| |/ /_/ / / / /_/ / __/
>>> /_/ |_|\__,_/_/ \__,_/_/
>>>
>>> Apache Karaf (4.0.8)
>>>
>>> Hit '<tab>' for a list of available commands
>>> and '[cmd] --help' for help on a specific command.
>>> Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
>>>
>>> karaf@root()> feature:repo-add camel 2.17.3
>>> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
>>> karaf@root()> feature:repo-add activemq 5.14.3
>>> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
>>> karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel activemq-broker-noweb activemq-blueprint
>>> karaf@root()> activemq:list
>>> brokerName = amq-broker
>>>
>>>
>>> Kindly tegards
>>> Krzysztof
>>>
>>> On 30.11.2016 14:11, IODB wrote:
>>>> Can somebody refer me to the relevant Jira issue, so I can track its
>>>> progress?
>>>>
>>>> Thanks
>>>>
>>>>
> Krzysztof Sobkowiak
>
> JEE & OSS Architect, Integration Architect
> Apache Software Foundation Member (http://apache.org/)
> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
> Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Sobkowiak Krzysztof <kr...@gmail.com>.
Btw, this trick with camel-cxf doesn't help with Camel 2.18.x. I think, there was a change in Camel 2.17.3 which helped with this problem (but not completely yet), but the change is not available in 2.18.x (I tried current snapshot and it didn't help too).
It looks like this change has helped in 2.17.3 https://github.com/apache/camel/commit/284cc6780de1e32468ef2ae50ad357a444e79da1 (CAMEL-10153), which introduces [3.2,5) as version range for spring in camel-cxf. In 2.18.x there is still used the version range [4.1,5)
Regards
Krzysztof
On 19.01.2017 01:17, Krzysztof Sobkowiak wrote:
> My mistake. This problem still happens in the sample steps below - the exception still occurs after Karaf restart and broker doesn't start.
> But adding camel-cxf seems to fix this problem
>
> feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel activemq-broker-noweb activemq-blueprint
>
> Kindly regards
> Krzysztof
>
>
> On 14.01.2017 22:55, Krzysztof Sobkowiak wrote:
>> Hi
>>
>> I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 (also 4.0.7):
>>
>>
>> __ __ ____
>> / //_/____ __________ _/ __/
>> / ,< / __ `/ ___/ __ `/ /_
>> / /| |/ /_/ / / / /_/ / __/
>> /_/ |_|\__,_/_/ \__,_/_/
>>
>> Apache Karaf (4.0.8)
>>
>> Hit '<tab>' for a list of available commands
>> and '[cmd] --help' for help on a specific command.
>> Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
>>
>> karaf@root()> feature:repo-add camel 2.17.3
>> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
>> karaf@root()> feature:repo-add activemq 5.14.3
>> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
>> karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel activemq-broker-noweb activemq-blueprint
>> karaf@root()> activemq:list
>> brokerName = amq-broker
>>
>>
>> Kindly tegards
>> Krzysztof
>>
>> On 30.11.2016 14:11, IODB wrote:
>>> Can somebody refer me to the relevant Jira issue, so I can track its
>>> progress?
>>>
>>> Thanks
>>>
>>>
Krzysztof Sobkowiak
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
My mistake. This problem still happens in the sample steps below - the exception still occurs after Karaf restart and broker doesn't start.
But adding camel-cxf seems to fix this problem
feature:install camel camel-blueprint camel-jms camel-cxf activemq-camel activemq-broker-noweb activemq-blueprint
Kindly regards
Krzysztof
On 14.01.2017 22:55, Krzysztof Sobkowiak wrote:
> Hi
>
> I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 (also 4.0.7):
>
>
> __ __ ____
> / //_/____ __________ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
>
> Apache Karaf (4.0.8)
>
> Hit '<tab>' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
>
> karaf@root()> feature:repo-add camel 2.17.3
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
> karaf@root()> feature:repo-add activemq 5.14.3
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
> karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel activemq-broker-noweb activemq-blueprint
> karaf@root()> activemq:list
> brokerName = amq-broker
>
>
> Kindly tegards
> Krzysztof
>
> On 30.11.2016 14:11, IODB wrote:
>> Can somebody refer me to the relevant Jira issue, so I can track its
>> progress?
>>
>> Thanks
>>
>>
>>
>> --
>> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048863.html
>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>
> --
> Krzysztof Sobkowiak (@ksobkowiak)
>
> JEE & OSS Architect, Integration Architect
> Apache Software Foundation Member (http://apache.org/)
> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
> Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Hi
I could successfully install Camel 2.17.3 and ActiveMQ 5.14.3 on Karaf 4.0.8 (also 4.0.7):
__ __ ____
/ //_/____ __________ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.0.8)
Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf@root()> feature:repo-add camel 2.17.3
Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.17.3/xml/features
karaf@root()> feature:repo-add activemq 5.14.3
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.14.3/xml/features
karaf@root()> feature:install camel camel-blueprint camel-jms activemq-camel activemq-broker-noweb activemq-blueprint
karaf@root()> activemq:list
brokerName = amq-broker
Kindly tegards
Krzysztof
On 30.11.2016 14:11, IODB wrote:
> Can somebody refer me to the relevant Jira issue, so I can track its
> progress?
>
> Thanks
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048863.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by IODB <iv...@caffeinated-consulting.com>.
Can somebody refer me to the relevant Jira issue, so I can track its
progress?
Thanks
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048863.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Krzysztof
I gonna work on this. Thanks !
Regards
JB
On 11/27/2016 04:10 PM, Krzysztof Sobkowiak wrote:
> Additional observation:
>
> Installing the activemq components leads to installation of 3 versions of Spring bundles
>
> la
> ---
> 96 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
> 97 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-aop
> 98 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
> 99 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
> 100 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-beans
> 101 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
> 102 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
> 103 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-context
> 104 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
> 105 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
> 106 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-context-support
> 107 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
> 108 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
> 109 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-core
> 110 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
> 111 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
> 112 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-expression
> 113 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
> 114 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-jms
> 115 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-jms
> 116 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-tx
> 117 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-tx
>
> Regards
> Krzysztof
>
>
> On 27.11.2016 15:58, Krzysztof Sobkowiak wrote:
>> I have just added following entry to activemq-osgi pom file in current ActiveMQ master
>>
>> org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
>>
>> The problem still exists, but everything looks ok with the wiring:
>>
>> karaf@root()> exports | grep org.apache.xbean.spring.context.v2
>> org.apache.xbean.spring.context.v2 | 4.2.0 | 123 | org.apache.xbean.spring
>> org.apache.xbean.spring.context.v2c | 4.2.0 | 123 | org.apache.xbean.spring
>>
>> karaf@root()> imports | grep org.apache.xbean.spring.context.v2
>> org.apache.xbean.spring.context.v2 | [3.13.0,5.0.0) | resolved | 66 | org.apache.activemq.activemq-osgi
>>
>> karaf@root()> bundle:classes 123 | grep XBeanNamespaceHandler
>> org/apache/xbean/spring/context/v2/XBeanNamespaceHandler.class
>> org/apache/xbean/spring/context/v2/XBeanNamespaceHandlerResolver.class
>> org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler$1.class
>> org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler.class
>>
>>
>> karaf@root()> headers 66
>>
>> activemq-osgi (66)
>> ------------------
>>
>> .....
>>
>> Import-Package =
>> com.fasterxml.jackson.annotation;resolution:=optional;version="[2.6,3)",
>> com.fasterxml.jackson.databind;resolution:=optional;version="[2.6,3)",
>> com.fasterxml.jackson.databind.annotation;resolution:=optional;version="[2.6,3)",
>> ....
>> org.apache.tools.ant;resolution:=optional,
>> org.apache.xbean.spring.context;resolution:=optional;version="[3.13,5)",
>> org.apache.xbean.spring.context.impl;resolution:=optional;version="[3.13,5)",
>> org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
>> org.apache.zookeeper;resolution:=optional;version="[3.4,4)",
>> org.apache.zookeeper.data;resolution:=optional;version="[3.4,4)",
>>
>>
>>
>> karaf@root()> headers 123
>>
>> Apache XBean :: Spring (123)
>> ----------------------------
>> .............
>> Export-Package =
>> .......
>> org.apache.xbean.spring.context.v2;
>> uses:="org.apache.xbean.spring.context,
>> org.springframework.beans,
>> org.springframework.beans.factory,
>> org.springframework.beans.factory.config,
>> org.springframework.beans.factory.support,
>> org.springframework.beans.factory.xml,
>> org.springframework.context,
>> org.springframework.core.io,
>> org.w3c.dom";
>> version=4.2,
>>
>>
>> So, the package seems to be correctly exported and wired to activemq-osgi. I cannot see any other exceptions in log. I tried to refresh/restart/re-resolve the bundles and the same effect. Altough the package is correctly wired and contains the necessery class, the class cannot be found in the activemq-osgi classpath.
>>
>> One additional observation, maybe it helps - bundle:requirements doesn't show xbean as requirement for activemq-osgi.
>>
>> karaf@root()> bundle:requirements 66 | grep org.apache.xbean
>> karaf@root()>
>>
>>
>>
>>
>> Kindly regards
>> Krzysztof
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 27.11.2016 14:09, Jean-Baptiste Onofr� wrote:
>>> Hi Krzysztof
>>>
>>> yup, it sounds like a missing import.
>>>
>>> I gonna take a look later today.
>>>
>>> Regards
>>> JB
>>>
>>> On 11/27/2016 01:54 PM, Krzysztof Sobkowiak wrote:
>>>> Hi
>>>>
>>>> I have tested it yesterday again on Karaf 4.0.7 with Camel 2.17.3 and ActiveMQ 5.14.1 and I can install activemq-broker an activemq-camel. But after restart I get following error
>>>>
>>>> Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [62]
>>>> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
>>>> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_111]
>>>> at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)[95:org.apache.servicemix.bundles.spring-core:4.2.5.RELEASE_1]
>>>> at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:125)[89:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1]
>>>>
>>>> I think, addidng import for org.apache.xbean.spring.context.v2 in activemq-osgi should help (at least as a workaround)
>>>>
>>>> Kindly regards
>>>> Krzysztof
>>>>
>>>>
>>>>
>>>> On 27.11.2016 12:24, Jean-Baptiste Onofr� wrote:
>>>>> Hi Christian,
>>>>>
>>>>> Please, ping me tomorrow we can sync/work together on that.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 11/27/2016 09:05 AM, Christian Schneider wrote:
>>>>>> My fixes were only touching activemq blueprint. I did not check the
>>>>>> ActiveMQ spring support.
>>>>>> This might be very relevant for TESB though. I will look into it tomorrow.
>>>>>>
>>>>>> Christian
>>>>>>
>>>>>>
>>>>>> 2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofr� <jb...@nanthrax.net>:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>>
>>>>>>> On 11/26/2016 09:44 PM, IODB wrote:
>>>>>>>
>>>>>>>> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> View this message in context: http://karaf.922171.n3.nabble.
>>>>>>>> com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
>>>>>>>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> Jean-Baptiste Onofr�
>>>>>>> jbonofre@apache.org
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>> --
>> Krzysztof Sobkowiak (@ksobkowiak)
>>
>> JEE & OSS Architect, Integration Architect
>> Apache Software Foundation Member (http://apache.org/)
>> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
>> Senior Application Consultant @ Capgemini SSC (http://www.capgeminisoftware.pl/)
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Additional observation:
Installing the activemq components leads to installation of 3 versions of Spring bundles
la
---
96 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
97 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-aop
98 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-aop
99 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
100 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-beans
101 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-beans
102 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
103 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-context
104 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context
105 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
106 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-context-support
107 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-context-support
108 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
109 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-core
110 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-core
111 | Active | 30 | 3.2.17.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
112 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-expression
113 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-expression
114 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-jms
115 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-jms
116 | Active | 30 | 4.1.7.RELEASE_2 | Apache ServiceMix :: Bundles :: spring-tx
117 | Active | 30 | 4.2.5.RELEASE_1 | Apache ServiceMix :: Bundles :: spring-tx
Regards
Krzysztof
On 27.11.2016 15:58, Krzysztof Sobkowiak wrote:
> I have just added following entry to activemq-osgi pom file in current ActiveMQ master
>
> org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
>
> The problem still exists, but everything looks ok with the wiring:
>
> karaf@root()> exports | grep org.apache.xbean.spring.context.v2
> org.apache.xbean.spring.context.v2 | 4.2.0 | 123 | org.apache.xbean.spring
> org.apache.xbean.spring.context.v2c | 4.2.0 | 123 | org.apache.xbean.spring
>
> karaf@root()> imports | grep org.apache.xbean.spring.context.v2
> org.apache.xbean.spring.context.v2 | [3.13.0,5.0.0) | resolved | 66 | org.apache.activemq.activemq-osgi
>
> karaf@root()> bundle:classes 123 | grep XBeanNamespaceHandler
> org/apache/xbean/spring/context/v2/XBeanNamespaceHandler.class
> org/apache/xbean/spring/context/v2/XBeanNamespaceHandlerResolver.class
> org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler$1.class
> org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler.class
>
>
> karaf@root()> headers 66
>
> activemq-osgi (66)
> ------------------
>
> .....
>
> Import-Package =
> com.fasterxml.jackson.annotation;resolution:=optional;version="[2.6,3)",
> com.fasterxml.jackson.databind;resolution:=optional;version="[2.6,3)",
> com.fasterxml.jackson.databind.annotation;resolution:=optional;version="[2.6,3)",
> ....
> org.apache.tools.ant;resolution:=optional,
> org.apache.xbean.spring.context;resolution:=optional;version="[3.13,5)",
> org.apache.xbean.spring.context.impl;resolution:=optional;version="[3.13,5)",
> org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
> org.apache.zookeeper;resolution:=optional;version="[3.4,4)",
> org.apache.zookeeper.data;resolution:=optional;version="[3.4,4)",
>
>
>
> karaf@root()> headers 123
>
> Apache XBean :: Spring (123)
> ----------------------------
> .............
> Export-Package =
> .......
> org.apache.xbean.spring.context.v2;
> uses:="org.apache.xbean.spring.context,
> org.springframework.beans,
> org.springframework.beans.factory,
> org.springframework.beans.factory.config,
> org.springframework.beans.factory.support,
> org.springframework.beans.factory.xml,
> org.springframework.context,
> org.springframework.core.io,
> org.w3c.dom";
> version=4.2,
>
>
> So, the package seems to be correctly exported and wired to activemq-osgi. I cannot see any other exceptions in log. I tried to refresh/restart/re-resolve the bundles and the same effect. Altough the package is correctly wired and contains the necessery class, the class cannot be found in the activemq-osgi classpath.
>
> One additional observation, maybe it helps - bundle:requirements doesn't show xbean as requirement for activemq-osgi.
>
> karaf@root()> bundle:requirements 66 | grep org.apache.xbean
> karaf@root()>
>
>
>
>
> Kindly regards
> Krzysztof
>
>
>
>
>
>
>
>
>
>
>
>
> On 27.11.2016 14:09, Jean-Baptiste Onofr� wrote:
>> Hi Krzysztof
>>
>> yup, it sounds like a missing import.
>>
>> I gonna take a look later today.
>>
>> Regards
>> JB
>>
>> On 11/27/2016 01:54 PM, Krzysztof Sobkowiak wrote:
>>> Hi
>>>
>>> I have tested it yesterday again on Karaf 4.0.7 with Camel 2.17.3 and ActiveMQ 5.14.1 and I can install activemq-broker an activemq-camel. But after restart I get following error
>>>
>>> Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [62]
>>> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
>>> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
>>> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_111]
>>> at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)[95:org.apache.servicemix.bundles.spring-core:4.2.5.RELEASE_1]
>>> at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:125)[89:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1]
>>>
>>> I think, addidng import for org.apache.xbean.spring.context.v2 in activemq-osgi should help (at least as a workaround)
>>>
>>> Kindly regards
>>> Krzysztof
>>>
>>>
>>>
>>> On 27.11.2016 12:24, Jean-Baptiste Onofr� wrote:
>>>> Hi Christian,
>>>>
>>>> Please, ping me tomorrow we can sync/work together on that.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 11/27/2016 09:05 AM, Christian Schneider wrote:
>>>>> My fixes were only touching activemq blueprint. I did not check the
>>>>> ActiveMQ spring support.
>>>>> This might be very relevant for TESB though. I will look into it tomorrow.
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> 2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofr� <jb...@nanthrax.net>:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>>>>>> On 11/26/2016 09:44 PM, IODB wrote:
>>>>>>
>>>>>>> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context: http://karaf.922171.n3.nabble.
>>>>>>> com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
>>>>>>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> Jean-Baptiste Onofr�
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
> --
> Krzysztof Sobkowiak (@ksobkowiak)
>
> JEE & OSS Architect, Integration Architect
> Apache Software Foundation Member (http://apache.org/)
> Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
> Senior Application Consultant @ Capgemini SSC (http://www.capgeminisoftware.pl/)
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Application Consultant @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
I have just added following entry to activemq-osgi pom file in current ActiveMQ master
org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
The problem still exists, but everything looks ok with the wiring:
karaf@root()> exports | grep org.apache.xbean.spring.context.v2
org.apache.xbean.spring.context.v2 | 4.2.0 | 123 | org.apache.xbean.spring
org.apache.xbean.spring.context.v2c | 4.2.0 | 123 | org.apache.xbean.spring
karaf@root()> imports | grep org.apache.xbean.spring.context.v2
org.apache.xbean.spring.context.v2 | [3.13.0,5.0.0) | resolved | 66 | org.apache.activemq.activemq-osgi
karaf@root()> bundle:classes 123 | grep XBeanNamespaceHandler
org/apache/xbean/spring/context/v2/XBeanNamespaceHandler.class
org/apache/xbean/spring/context/v2/XBeanNamespaceHandlerResolver.class
org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler$1.class
org/apache/xbean/spring/context/v2c/XBeanNamespaceHandler.class
karaf@root()> headers 66
activemq-osgi (66)
------------------
.....
Import-Package =
com.fasterxml.jackson.annotation;resolution:=optional;version="[2.6,3)",
com.fasterxml.jackson.databind;resolution:=optional;version="[2.6,3)",
com.fasterxml.jackson.databind.annotation;resolution:=optional;version="[2.6,3)",
....
org.apache.tools.ant;resolution:=optional,
org.apache.xbean.spring.context;resolution:=optional;version="[3.13,5)",
org.apache.xbean.spring.context.impl;resolution:=optional;version="[3.13,5)",
org.apache.xbean.spring.context.v2;resolution:=optional;version="[3.13,5)",
org.apache.zookeeper;resolution:=optional;version="[3.4,4)",
org.apache.zookeeper.data;resolution:=optional;version="[3.4,4)",
karaf@root()> headers 123
Apache XBean :: Spring (123)
----------------------------
.............
Export-Package =
.......
org.apache.xbean.spring.context.v2;
uses:="org.apache.xbean.spring.context,
org.springframework.beans,
org.springframework.beans.factory,
org.springframework.beans.factory.config,
org.springframework.beans.factory.support,
org.springframework.beans.factory.xml,
org.springframework.context,
org.springframework.core.io,
org.w3c.dom";
version=4.2,
So, the package seems to be correctly exported and wired to activemq-osgi. I cannot see any other exceptions in log. I tried to refresh/restart/re-resolve the bundles and the same effect. Altough the package is correctly wired and contains the necessery class, the class cannot be found in the activemq-osgi classpath.
One additional observation, maybe it helps - bundle:requirements doesn't show xbean as requirement for activemq-osgi.
karaf@root()> bundle:requirements 66 | grep org.apache.xbean
karaf@root()>
Kindly regards
Krzysztof
On 27.11.2016 14:09, Jean-Baptiste Onofr� wrote:
> Hi Krzysztof
>
> yup, it sounds like a missing import.
>
> I gonna take a look later today.
>
> Regards
> JB
>
> On 11/27/2016 01:54 PM, Krzysztof Sobkowiak wrote:
>> Hi
>>
>> I have tested it yesterday again on Karaf 4.0.7 with Camel 2.17.3 and ActiveMQ 5.14.1 and I can install activemq-broker an activemq-camel. But after restart I get following error
>>
>> Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [62]
>> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
>> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
>> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_111]
>> at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)[95:org.apache.servicemix.bundles.spring-core:4.2.5.RELEASE_1]
>> at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:125)[89:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1]
>>
>> I think, addidng import for org.apache.xbean.spring.context.v2 in activemq-osgi should help (at least as a workaround)
>>
>> Kindly regards
>> Krzysztof
>>
>>
>>
>> On 27.11.2016 12:24, Jean-Baptiste Onofr� wrote:
>>> Hi Christian,
>>>
>>> Please, ping me tomorrow we can sync/work together on that.
>>>
>>> Regards
>>> JB
>>>
>>> On 11/27/2016 09:05 AM, Christian Schneider wrote:
>>>> My fixes were only touching activemq blueprint. I did not check the
>>>> ActiveMQ spring support.
>>>> This might be very relevant for TESB though. I will look into it tomorrow.
>>>>
>>>> Christian
>>>>
>>>>
>>>> 2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofr� <jb...@nanthrax.net>:
>>>>
>>>>> Hi,
>>>>>
>>>>> Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 11/26/2016 09:44 PM, IODB wrote:
>>>>>
>>>>>> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context: http://karaf.922171.n3.nabble.
>>>>>> com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
>>>>>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>> --
>>>>> Jean-Baptiste Onofr�
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Application Consultant @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Krzysztof
yup, it sounds like a missing import.
I gonna take a look later today.
Regards
JB
On 11/27/2016 01:54 PM, Krzysztof Sobkowiak wrote:
> Hi
>
> I have tested it yesterday again on Karaf 4.0.7 with Camel 2.17.3 and ActiveMQ 5.14.1 and I can install activemq-broker an activemq-camel. But after restart I get following error
>
> Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [62]
> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
> at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_111]
> at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)[95:org.apache.servicemix.bundles.spring-core:4.2.5.RELEASE_1]
> at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:125)[89:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1]
>
> I think, addidng import for org.apache.xbean.spring.context.v2 in activemq-osgi should help (at least as a workaround)
>
> Kindly regards
> Krzysztof
>
>
>
> On 27.11.2016 12:24, Jean-Baptiste Onofr� wrote:
>> Hi Christian,
>>
>> Please, ping me tomorrow we can sync/work together on that.
>>
>> Regards
>> JB
>>
>> On 11/27/2016 09:05 AM, Christian Schneider wrote:
>>> My fixes were only touching activemq blueprint. I did not check the
>>> ActiveMQ spring support.
>>> This might be very relevant for TESB though. I will look into it tomorrow.
>>>
>>> Christian
>>>
>>>
>>> 2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofr� <jb...@nanthrax.net>:
>>>
>>>> Hi,
>>>>
>>>> Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 11/26/2016 09:44 PM, IODB wrote:
>>>>
>>>>> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context: http://karaf.922171.n3.nabble.
>>>>> com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
>>>>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>> --
>>>> Jean-Baptiste Onofr�
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>>
>>>
>>
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Hi
I have tested it yesterday again on Karaf 4.0.7 with Camel 2.17.3 and ActiveMQ 5.14.1 and I can install activemq-broker an activemq-camel. But after restart I get following error
Caused by: java.lang.ClassNotFoundException: org.apache.xbean.spring.context.v2.XBeanNamespaceHandler not found by org.apache.activemq.activemq-osgi [62]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1574)[org.apache.felix.framework-5.4.0.jar:]
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)[org.apache.felix.framework-5.4.0.jar:]
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018)[org.apache.felix.framework-5.4.0.jar:]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)[:1.8.0_111]
at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)[95:org.apache.servicemix.bundles.spring-core:4.2.5.RELEASE_1]
at org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.resolve(DefaultNamespaceHandlerResolver.java:125)[89:org.apache.servicemix.bundles.spring-beans:4.2.5.RELEASE_1]
I think, addidng import for org.apache.xbean.spring.context.v2 in activemq-osgi should help (at least as a workaround)
Kindly regards
Krzysztof
On 27.11.2016 12:24, Jean-Baptiste Onofr� wrote:
> Hi Christian,
>
> Please, ping me tomorrow we can sync/work together on that.
>
> Regards
> JB
>
> On 11/27/2016 09:05 AM, Christian Schneider wrote:
>> My fixes were only touching activemq blueprint. I did not check the
>> ActiveMQ spring support.
>> This might be very relevant for TESB though. I will look into it tomorrow.
>>
>> Christian
>>
>>
>> 2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofr� <jb...@nanthrax.net>:
>>
>>> Hi,
>>>
>>> Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 11/26/2016 09:44 PM, IODB wrote:
>>>
>>>> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context: http://karaf.922171.n3.nabble.
>>>> com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
>>>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>>>
>>>>
>>> --
>>> Jean-Baptiste Onofr�
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
>>
>
--
Krzysztof Sobkowiak (@ksobkowiak)
JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Application Consultant @ Capgemini SSC (http://www.capgeminisoftware.pl/)
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Christian,
Please, ping me tomorrow we can sync/work together on that.
Regards
JB
On 11/27/2016 09:05 AM, Christian Schneider wrote:
> My fixes were only touching activemq blueprint. I did not check the
> ActiveMQ spring support.
> This might be very relevant for TESB though. I will look into it tomorrow.
>
> Christian
>
>
> 2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofr� <jb...@nanthrax.net>:
>
>> Hi,
>>
>> Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
>>
>> Regards
>> JB
>>
>>
>> On 11/26/2016 09:44 PM, IODB wrote:
>>
>>> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>>>
>>>
>>>
>>> --
>>> View this message in context: http://karaf.922171.n3.nabble.
>>> com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
>>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>>
>>>
>> --
>> Jean-Baptiste Onofr�
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Christian Schneider <ch...@die-schneider.net>.
My fixes were only touching activemq blueprint. I did not check the
ActiveMQ spring support.
This might be very relevant for TESB though. I will look into it tomorrow.
Christian
2016-11-27 6:18 GMT+01:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi,
>
> Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
>
> Regards
> JB
>
>
> On 11/26/2016 09:44 PM, IODB wrote:
>
>> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>>
>>
>>
>> --
>> View this message in context: http://karaf.922171.n3.nabble.
>> com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
--
Christian Schneider
http://www.liquid-reality.de
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de>
Open Source Architect
http://www.talend.com
<https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com>
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
Christian did some fixes recently. Did you check with a ActiveMQ SNAPSHOT ?
Regards
JB
On 11/26/2016 09:44 PM, IODB wrote:
> Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>
--
Jean-Baptiste Onofr
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: ActiveMQ and Camel 2.17.x on Karaf
Posted by IODB <iv...@caffeinated-consulting.com>.
Issue still exists with ActiveMQ 5.14.1 - Camel 2.18.0 - Karaf 4.0.7
--
View this message in context: http://karaf.922171.n3.nabble.com/ActiveMQ-and-Camel-2-17-x-on-Karaf-tp4046427p4048826.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.