Yep, it's about the camel vm component. I'm using 2.9.0. But yesterday I've managed to resolve the issue: It seems that after cameContext restart previously created producerTemplates are no longer valid since they've been created by the camecontext with the old component . . . If I create a new producerTemplate after the restart everything is ok. I will try with restarting the template because creating a new each time is quite expensive.
On Fri, Sep 14, 2012 at 9:07 AM, Claus Ibsen-2 [via Camel] < [email protected]> wrote: > On Thu, Sep 13, 2012 at 5:42 PM, shindito <[hidden > email]<http://user/SendEmail.jtp?type=node&node=5719338&i=0>> > 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: [hidden email]<http://user/SendEmail.jtp?type=node&node=5719338&i=1> > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/How-does-a-Camel-component-update-gets-reflected-by-existing-routes-tp5719275p5719338.html > To unsubscribe from How does a Camel component update gets reflected by > existing routes, click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5719275&code=YXRhbmFzLnNoaW5kb3ZAZ21haWwuY29tfDU3MTkyNzV8NDUyMzYxMTg=> > . > NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://camel.465427.n5.nabble.com/How-does-a-Camel-component-update-gets-reflected-by-existing-routes-tp5719275p5719349.html Sent from the Camel - Users mailing list archive at Nabble.com.
