You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by djtom <m_...@yahoo.com> on 2012/11/12 17:04:56 UTC
slf4j library of OSGi bundle cannot found in a SE (JBI Component)
Hi,
I created an OSGi bundle which uses ehcache-core library. In turn, ehcache
library uses slf4j logging, therefore I already included the slf4j jars in
the dependencies of the OSGi bundle. My bundle works well as a separate OSGi
bundle in servicemix. However, if I use the OSGi bundle from a SE (I created
a JBI Component), the following exception occurs (I checked SE zip file, it
has my OSGi bundle as a jar, and the OSGi bundle has slf4j-api and
slf4j-jdk14 jars. Moreover, service engine always asks for 1.5.8 version of
slf4j jar even if I use 1.6.0):
java.lang.NoClassDefFoundError: org/apache/log4j/Level
at
org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:223)[slf4j-api-1.5.8.jar:1.5.8]
at
org.slf4j.LoggerFactory.bind(LoggerFactory.java:120)[slf4j-api-1.5.8.jar:1.5.8]
at
org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)[slf4j-api-1.5.8.jar:1.5.8]
at
org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:269)[slf4j-api-1.5.8.jar:1.5.8]
at
org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:242)[slf4j-api-1.5.8.jar:1.5.8]
at
org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:255)[slf4j-api-1.5.8.jar:1.5.8]
at
net.sf.ehcache.CacheManager.<clinit>(CacheManager.java:131)[ehcache-core-2.6.0.jar:]
at
de.unistuttgart.iaas.jbimulti2.cache.CacheFactory.getCache(CacheFactory.java:16)[jbi.servicemix.registry-1.0.jar:]
at
de.unistuttgart.iaas.jbimulti2.registry.ServiceRegistry.<init>(ServiceRegistry.java:35)[jbi.servicemix.registry-1.0.jar:]
at
de.unistuttgart.iaas.jbimulti2.jbi.servicemix.dsds.DSDSEndpoint.processInOut(DSDSEndpoint.java:72)[servicemix-dsds-2011.01.jar:2011.01]
at
org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:111)[servicemix-common-2011.01.jar:2011.01]
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:651)[servicemix-common-2011.01.jar:2011.01]
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:606)[servicemix-common-2011.01.jar:2011.01]
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchangeInTx(AsyncBaseLifeCycle.java:501)[servicemix-common-2011.01.jar:2011.01]
at
org.apache.servicemix.common.AsyncBaseLifeCycle$2.run(AsyncBaseLifeCycle.java:370)[servicemix-common-2011.01.jar:2011.01]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.6.0_20]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.6.0_20]
at java.lang.Thread.run(Thread.java:636)[:1.6.0_20]
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Level in
classloader servicemix-shared
at
org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:206)[125:org.apache.servicemix.jbi.deployer:1.4.0]
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)[:1.6.0_20]
--
View this message in context: http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: slf4j library of OSGi bundle cannot found in a SE (JBI
Component)
Posted by djtom <m_...@yahoo.com>.
Thanks for the help Freeman.
I have everything you mentioned, my SE is a OSGi bundle (I have taken a look
at other SEs and everything is ok). Moreover, I don't use SMX 3.x but SMX
4.3.0 version.
By the way, I call my 'jbi.servicemix.registry' OSGi bundle (it is not
bluepring bundle, simply OSGi jar packaged bundle) class functions
successfully when I don't call ehcache library classes that use slf4j
logging. That means, I am using the OSGi bundle as a library in the SE.
--
View this message in context: http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899p5714909.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: slf4j library of OSGi bundle cannot found in a SE (JBI Component)
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
Ensure your customer SeviceEngine also OSGi friendly.
What works in SMX 3.x doesn't mean it also works in SMX 4.x.
Firstly, your customer SeviceEngine should also be a OSGi bundle, it should use blueprint(or spring-dm) to expose an OSGi service which implements the javax.jbi.component.Component interface, so it could be wired dynamically. Please take a look at servicemix-camel SE[1] or other SE shipped with Servicemix as an example.
[1]https://svn.apache.org/repos/asf/servicemix/components/trunk/engines/servicemix-camel/
Freeman
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
On 2012-11-13, at 下午6:47, djtom wrote:
> yes I did it. It was just example, my bean.xml file is as following:
>
>
> <beans
> xmlns:dsdsComponent="http://dsds.iaas.uni-stuttgart.de/dsds-component/1.0"
> xmlns:dsds="http://jbimulti2.iaas.uni-stuttgart.de/dsds"
> xmlns="http://www.springframework.org/schema/beans"
> xmlns:xsi="http://http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://servicemix.apache.org/http/1.0
> http://servicemix.apache.org/schema/servicemix-http-3.2.3.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
>
> <dsdsComponent:endpoint service="dsds:dsdsService"
> endpoint="dsdsEndpoint"/>
>
> <classpath>
> <library>osgi:jbi.servicemix.registry</library>
> </classpath>
>
> </beans>
>
> where, "http://dsds.iaas.uni-stuttgart.de/dsds-component/1.0" is name space
> of my newly created SE.
> "jbi.servicemix.registry" is symbolic name of my OSGi bundle.
>
>
>
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899p5714907.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: slf4j library of OSGi bundle cannot found in a SE (JBI
Component)
Posted by djtom <m_...@yahoo.com>.
yes I did it. It was just example, my bean.xml file is as following:
<beans
xmlns:dsdsComponent="http://dsds.iaas.uni-stuttgart.de/dsds-component/1.0"
xmlns:dsds="http://jbimulti2.iaas.uni-stuttgart.de/dsds"
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://servicemix.apache.org/http/1.0
http://servicemix.apache.org/schema/servicemix-http-3.2.3.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">
<dsdsComponent:endpoint service="dsds:dsdsService"
endpoint="dsdsEndpoint"/>
<classpath>
<library>osgi:jbi.servicemix.registry</library>
</classpath>
</beans>
where, "http://dsds.iaas.uni-stuttgart.de/dsds-component/1.0" is name space
of my newly created SE.
"jbi.servicemix.registry" is symbolic name of my OSGi bundle.
--
View this message in context: http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899p5714907.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: slf4j library of OSGi bundle cannot found in a SE (JBI Component)
Posted by Freeman Fang <fr...@gmail.com>.
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
On 2012-11-13, at 下午6:26, djtom wrote:
> Hi,
>
> Thanks for the reply.
>
> I configured my SE with a SU as shown in tutorial of servicemix (I use
> servicemix 4.3.0), which is packaged in a different SA. It means, the SE and
> SA are different deployment zip files. The SU simply exposes endpoint and
> service of the SE. I have doubt that if I put the following snippet in
> bean.xml, first of all it does not work, of the SU:
>
> <beans xmlns:ds=".."
> xmlns:se="name space of my service engine">
>
> <se:endpoint service="ds:service" endpoint="dsEndpoint"/>
>
> <classpath>
> <library>osgi:Bundle-SymbolicName</library>
You need replace the "Bundle-SymbolicName" with the actual bundle SymbolicName of each bundle you wanna refer
> </classpath>
>
> </beans>
>
>
> After putting the classpath like above bean.xml, I got the following
> exception (but it works if I put the class path in xbean.xml which use
> servicemix build-in component, such as servicemix-http):
>
> 10:13:24,194 | ERROR | l Console Thread | ServiceAssemblyInstaller |
> ? ? | 125 -
> org.apache.servicemix.jbi.deployer - 1.4.0 | Error deploying SU dsds-su
> javax.jbi.management.DeploymentException: <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
> <component-name>servicemix-dsds</component-name>
> <component-task-result-details>
> <task-result-details>
> <task-id>deploy</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> <task-status-msg><msg-loc-info><loc-token/><loc-message>Could not deploy
> xbean service unit</loc-message></msg-loc-info></task-status-msg>
> <exception-info>
> <nesting-level>1</nesting-level>
> <msg-loc-info>
> <loc-token />
> <loc-message>Unexpected exception parsing XML document from file
> [/home/ubuntu/TaxiScenarioMultiTenant/apache-servicemix-4.3.0/data/jbi/dsds-http-sa/sus/dsds-su/xbean.xml];
> nested exception is java.lang.UnsupportedOperationException: Can not access
> shared libraries</loc-message>
>
> <stack-trace><![CDATA[org.springframework.beans.factory.BeanDefinitionStoreException:
> Unexpected exception parsing XML document from file
> [/home/ubuntu/TaxiScenarioMultiTenant/apache-servicemix-4.3.0/data/jbi/dsds-http-sa/sus/dsds-su/xbean.xml];
> nested exception is java.lang.UnsupportedOperationException: Can not access
> shared libraries
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:412)
> 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:143)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212)
> at
> org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:126)
> at
> org.apache.xbean.spring.context.FileSystemXmlApplicationContext.loadBeanDefinitions(FileSystemXmlApplicationContext.java:168)
> at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
> at
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
> at
> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:88)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
> at
> org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:104)
> at
> org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:207)
> at
> org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)
> at
> org.apache.servicemix.jbi.deployer.impl.Deployer.onBundleStarted(Deployer.java:334)
> at
> org.apache.servicemix.jbi.deployer.impl.Deployer.bundleChanged(Deployer.java:264)
> at
> org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:807)
> at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:729)
> at
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610)
> ...
>
>
>
>
>
>
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899p5714904.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: slf4j library of OSGi bundle cannot found in a SE (JBI
Component)
Posted by djtom <m_...@yahoo.com>.
Hi,
Thanks for the reply.
I configured my SE with a SU as shown in tutorial of servicemix (I use
servicemix 4.3.0), which is packaged in a different SA. It means, the SE and
SA are different deployment zip files. The SU simply exposes endpoint and
service of the SE. I have doubt that if I put the following snippet in
bean.xml, first of all it does not work, of the SU:
<beans xmlns:ds=".."
xmlns:se="name space of my service engine">
<se:endpoint service="ds:service" endpoint="dsEndpoint"/>
<classpath>
<library>osgi:Bundle-SymbolicName</library>
</classpath>
</beans>
After putting the classpath like above bean.xml, I got the following
exception (but it works if I put the class path in xbean.xml which use
servicemix build-in component, such as servicemix-http):
10:13:24,194 | ERROR | l Console Thread | ServiceAssemblyInstaller |
? ? | 125 -
org.apache.servicemix.jbi.deployer - 1.4.0 | Error deploying SU dsds-su
javax.jbi.management.DeploymentException: <component-task-result
xmlns="http://java.sun.com/xml/ns/jbi/management-message">
<component-name>servicemix-dsds</component-name>
<component-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg><msg-loc-info><loc-token/><loc-message>Could not deploy
xbean service unit</loc-message></msg-loc-info></task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<msg-loc-info>
<loc-token />
<loc-message>Unexpected exception parsing XML document from file
[/home/ubuntu/TaxiScenarioMultiTenant/apache-servicemix-4.3.0/data/jbi/dsds-http-sa/sus/dsds-su/xbean.xml];
nested exception is java.lang.UnsupportedOperationException: Can not access
shared libraries</loc-message>
<stack-trace><![CDATA[org.springframework.beans.factory.BeanDefinitionStoreException:
Unexpected exception parsing XML document from file
[/home/ubuntu/TaxiScenarioMultiTenant/apache-servicemix-4.3.0/data/jbi/dsds-http-sa/sus/dsds-su/xbean.xml];
nested exception is java.lang.UnsupportedOperationException: Can not access
shared libraries
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:412)
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:143)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212)
at
org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:126)
at
org.apache.xbean.spring.context.FileSystemXmlApplicationContext.loadBeanDefinitions(FileSystemXmlApplicationContext.java:168)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
at
org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:88)
at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
at
org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
at
org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:104)
at
org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:207)
at
org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)
at
org.apache.servicemix.jbi.deployer.impl.Deployer.onBundleStarted(Deployer.java:334)
at
org.apache.servicemix.jbi.deployer.impl.Deployer.bundleChanged(Deployer.java:264)
at
org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:807)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:729)
at
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610)
...
--
View this message in context: http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899p5714904.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
Re: slf4j library of OSGi bundle cannot found in a SE (JBI Component)
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
To deploy JBI SA/SU in OSGi container, you shouldn't embed any bundle jars, you should just refer them in your xbean.xml, the pattern is like
<classpath>
<library>osgi:Bundle-SymbolicName</library>
</classpath>
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
On 2012-11-13, at 上午12:04, djtom wrote:
> Hi,
>
> I created an OSGi bundle which uses ehcache-core library. In turn, ehcache
> library uses slf4j logging, therefore I already included the slf4j jars in
> the dependencies of the OSGi bundle. My bundle works well as a separate OSGi
> bundle in servicemix. However, if I use the OSGi bundle from a SE (I created
> a JBI Component), the following exception occurs (I checked SE zip file, it
> has my OSGi bundle as a jar, and the OSGi bundle has slf4j-api and
> slf4j-jdk14 jars. Moreover, service engine always asks for 1.5.8 version of
> slf4j jar even if I use 1.6.0):
>
> java.lang.NoClassDefFoundError: org/apache/log4j/Level
> at
> org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:223)[slf4j-api-1.5.8.jar:1.5.8]
> at
> org.slf4j.LoggerFactory.bind(LoggerFactory.java:120)[slf4j-api-1.5.8.jar:1.5.8]
> at
> org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111)[slf4j-api-1.5.8.jar:1.5.8]
> at
> org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:269)[slf4j-api-1.5.8.jar:1.5.8]
> at
> org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:242)[slf4j-api-1.5.8.jar:1.5.8]
> at
> org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:255)[slf4j-api-1.5.8.jar:1.5.8]
> at
> net.sf.ehcache.CacheManager.<clinit>(CacheManager.java:131)[ehcache-core-2.6.0.jar:]
> at
> de.unistuttgart.iaas.jbimulti2.cache.CacheFactory.getCache(CacheFactory.java:16)[jbi.servicemix.registry-1.0.jar:]
> at
> de.unistuttgart.iaas.jbimulti2.registry.ServiceRegistry.<init>(ServiceRegistry.java:35)[jbi.servicemix.registry-1.0.jar:]
> at
> de.unistuttgart.iaas.jbimulti2.jbi.servicemix.dsds.DSDSEndpoint.processInOut(DSDSEndpoint.java:72)[servicemix-dsds-2011.01.jar:2011.01]
> at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:111)[servicemix-common-2011.01.jar:2011.01]
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:651)[servicemix-common-2011.01.jar:2011.01]
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:606)[servicemix-common-2011.01.jar:2011.01]
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchangeInTx(AsyncBaseLifeCycle.java:501)[servicemix-common-2011.01.jar:2011.01]
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle$2.run(AsyncBaseLifeCycle.java:370)[servicemix-common-2011.01.jar:2011.01]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)[:1.6.0_20]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)[:1.6.0_20]
> at java.lang.Thread.run(Thread.java:636)[:1.6.0_20]
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Level in
> classloader servicemix-shared
> at
> org.apache.xbean.classloader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:206)[125:org.apache.servicemix.jbi.deployer:1.4.0]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:266)[:1.6.0_20]
>
>
>
>
> --
> View this message in context: http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.