On Thu, Sep 13, 2012 at 5:42 PM, shindito <atanas.shin...@gmail.com> wrote: > So, I have two types of routes: > 1) from vm:... to jms:topic.. > 2) from jms:topic... to user processor > > I've tried restarting the routes while changing the component - after that > the second type of routes still consume from the old jms provider ... and > these consuming from vm don't work at all > > But If I restart the whole context, the 2) routes start consuming from the > new jms Provider (as expected)! But still, the routes from vm do not work > after the restart . . . >
And the vm is the Camel VM component, not the in-memory vm transport of AMQ? What version of Camel do you use? And if you run in some container, try creating a plain unit test, that runs outside the container. To rule out any container weirdness. > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-does-a-Camel-component-update-gets-reflected-by-existing-routes-tp5719275p5719309.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
