I don’t know enough about how you are doing this to be sure, but this sounds suspiciously similar to an issue I’ve been fighting for quite a while now. I don’t know if it applies, but you may want to look at the workaround in this ticket ( https://issues.apache.org/jira/browse/CAMEL-9570 <https://issues.apache.org/jira/browse/CAMEL-9570> ) - the one using SimpleCamelBlueprintContext and see if that might help.
> On Dec 15, 2016, at 9:26 AM, yogu13 <yog...@gmail.com> wrote: > > Hi, > > I hit across a strange issue with camel 2.16.3 in karaf 4.0.5. The issue is > we have camel with few other components (blueprint, activemq, jaxb etc) > installed in karaf 4. I have a bundle which has route defined along with a > converter (using @converter ) annotation and FQCN mentioned as part of > META-INF/services/org/apache/camel/TypeConverter. On start of karaf the > bundle works fine along with the route. However If i make any changes to > this bundle and refresh it again, I get a exception on invocation of the > route. > > org.apache.camel.InvalidPayloadException > No body available of type:com.xxx.xxx.xxx > > The bundle state is active and i do not see any errors in karaf log file on > refresh of the bundle. To make this route work again I either have to > restart the camel-core bundle or restart karaf. > > Could it be camel-core is not releasing the previous classloader of > refreshed bundle?? Not sure if this has been reported by anyone. > > Regards, > -Yogesh > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-core-not-detecting-converters-on-bundle-restart-in-karaf4-tp5791503.html > Sent from the Camel - Users mailing list archive at Nabble.com.
