I tried adding the VM component as a separate OSGI service e.g.
And then used a reference to the service in my 2 separate camel routes e.g. And change the from/to uri to be e.g. <from uri="sharedvm:TestQ"> This worked ok when initially installed but displayed the same VM queue disconnected behaviour when I did a bundle update on route2. Partial good news is a bundle update on route1 does function okay. I next tried using the Hazelcast:seda component instead of VM and found that it worked perfectly through bundle updates of either route1 or route2. I would really love to use this instead of VM because it is is a clustered solution and seems to be performant. Unfortunately this component does not seem to support request/reply which I need for my usecase. So any other ideas? Thanks Steve -- View this message in context: http://camel.465427.n5.nabble.com/VM-Queues-Disconnected-after-Karaf-Bundle-Update-tp5727205p5727345.html Sent from the Camel - Users mailing list archive at Nabble.com.
