[ 
https://issues.apache.org/jira/browse/SM-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084708#comment-14084708
 ] 

Ge@@ru commented on SM-2353:
----------------------------

In a complex scenario that isn't so easy to create I received same error yet 
when both bundle are with blueprint implementation.
Probably, it isn't only a spring bundle problem.

> Cellar-Dosgi-2.3.2 between spring osgi service and blueprint osgi client 
> doesn't work from remote
> -------------------------------------------------------------------------------------------------
>
>                 Key: SM-2353
>                 URL: https://issues.apache.org/jira/browse/SM-2353
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 5.1.0
>            Reporter: Ge@@ru
>             Fix For: 5.1.x, 5.2.x, 6.0.x
>
>         Attachments: test-dosgi.zip
>
>
> Hi at all.
> I don't know if this issue is on correct site, probably is relative to aries 
> blueprint library but I test this only on ServiceMix and I don't if could be 
> relative to another problem.
> On smx-5.1.0 I installed cellar and cellar-dosgi version 2.3.2 and I create a 
> cluster between two node.
> On node1 is deployed an osgi service, on node2 is deployed a camel route that 
> call osgi service.
> If both bundle are created as blueprint bundle all works fine, if instead 
> osgi service is deployed as spring osgi service than I receive this exception:
> smx@root> java.lang.IllegalStateException: getService() returned null for 
> [it.test.helloword.HelloWord]
>       at 
> org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:249)
>       at 
> org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:55)
>       at 
> org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:298)
>       at Proxyd21dbd0b_6b77_42a0_9d13_5a645ec2fc48.hello(Unknown Source)
>       at it.test.HelloWordBean.callOsgiService(HelloWordBean.java:33)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:606)
>       at 
> org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:407)
>       at 
> org.apache.camel.component.bean.MethodInfo$1.doProceed(MethodInfo.java:278)
>       at 
> org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:251)
>       at 
> org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:166)
>       at 
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
>       at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:398)
>       at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)
>       at org.apache.camel.processor.Pipeline.process(Pipeline.java:118)
>       at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
>       at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)
>       at 
> org.apache.camel.processor.loadbalancer.QueueLoadBalancer.process(QueueLoadBalancer.java:43)
>       at 
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:105)
>       at 
> org.apache.camel.processor.loadbalancer.LoadBalancerSupport.process(LoadBalancerSupport.java:87)
>       at 
> org.apache.camel.component.quartz.QuartzEndpoint.onJobExecute(QuartzEndpoint.java:115)
>       at org.apache.camel.component.quartz.CamelJob.execute(CamelJob.java:61)
>       at org.quartz.core.JobRunShell.run(JobRunShell.java:223)
>       at 
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
> If I use spring osgi service and blueprint client on same instance all works 
> fine.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to