You may need to install camel prior in MQ 7.1.
And then install your custom bundle afterwards.
I had installed the camel feature prior to installing the bundle. But still i saw the exception.
However, the bundle started working after MQ restart. No issues.
Thanks for the suggestion.
Oh are you using spring XML or OSGi Blueprint in your custom application? When using spring xml (eg spring-dm) it may require existing bundles to be refreshed when you do hot deployment. eg sometimes you may see a message saying bundle XXXX refreshed or something like that.
And hence after a restart of the JVM it would work fine, as there is no hot deployment happening.
So when using spring xml / spring-dm just be a bit more observant about you may need to restart / refresh bundles manually etc to get it working when hot deploying.
OSGi blueprint is better designed for this, and generally just works.