Thank you for the information.
I tried to remind myself to include version information, but forgot by the time I reached the end of my post.
We are using FUSE 4.3.1-01-15, which uses Camel 2.6.0-fuse-01-15 (I believe).
Do you know when it was fixed?
Is there some workaround besides upgrading Camel?
We are being used as a framework, so upgrading would be quite disruptive and we'd like to avoid that as a solution if at all possible.
When sending between CamelContext over VM, then you possible have to copy the Exchange and set a the correct CamelContext.
See the preapareExchange method of the seda endpoint
Thanks once again for the information.
Let me just make sure I understand your advice.
Would I create a bean that contains the code from the prepareExchange method?
And then insert it into my existing route like the following:
I think I would create a custom Camel endpoint so that I could have access to the correct Camel context.
Does the above sound correct?
I suggest to test that each of the camel applications works independetly. For example kicking off a route using a timer endpoint. And make sure the properties resolver works.
Then you know that its when you send from one camel to another over VM that you have this problem. If thats the case then its most likely due to that bug I talked above before.