Thanks astefanutti, appreciate you help!
We are not using BeanManagerProvider but
javax.enterprise.inject.spi.BeanManager. 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.
