> On 15 Jun 2016, at 17:19, saysvishal <[email protected]> wrote: > > Thanks astefanutti, appreciate you help! > > We are not using BeanManagerProvider but > javax.enterprise.inject.spi.BeanManager.
Sorry I haven’t been clear. I meant that Camel CDI, prior to Camel 2.17.0, relies on DeltaSpike’s BeanManagerProvider while it should not [1]. Unfortunately BeanManagerProvider relies on ThreadLocal and static state that makes it hard to troubleshoot issues as the one you face. If you cannot upgrade Camel, my best advise would be at least trying to use the camel-cdi JAR from Camel 2.17.0 by doing the adaptation to camel-core 2.12, which should be small. Otherwise, you’ll need to investigate further and gets into the BeanManagerProvider internals. Antonin [1]: https://issues.apache.org/jira/browse/CAMEL-6338 > But I looked at 2.17 camel patch > and its fixes. Its targeted for many CDI BeanManager Component loading > issues which covers one this issue. > https://issues.apache.org/jira/browse/CAMEL-9201 > > We are using 2.12 and don't have any sooner plan to upgrade it 2.17 as its > being used and part of large integration system. > Is there any other work around instead of upgrading camel version? > > One of the big challenge for us reproducing this issue, as it happened for 1 > day and goes off after jboss restart. I believed, as we have context > clear/destroy might helped. > > @PreDestroy > private void OnCloseTest() throws Exception { > ctx.getContext().stop(); > } > > > Thanks again for your help. Appreciated. > > regards, > Vishal > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/RuntimeCamelException-java-lang-IllegalStateException-Unable-to-find-BeanManager-Please-ensure-that-y-tp5784059p5784096.html > Sent from the Camel - Users mailing list archive at Nabble.com.
