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 pr
On Thu, Sep 13, 2012 at 5:42 PM, shindito 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 prov
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 I
Hi
Yeah give them a try.
Notice #2 - shutting down a CamelContext, and starting the same
CamelContext instance again, is not guaranteed to properly startup
again. As you may have used some custom components / resources /
whatever, which safely cannot be-restarted again.
But still give it a try a
Thanks for the prompt reply!
Just to clarify: shutting down all the routes will not require a
camelcontext restart?
So, I have to options:
1) Stop all routes -> shutdown old component -> add new component -> start
new component -> start all routes
2) Stop context -> shutdown old component -> add
And start the routes again.
> If not, what is the "Camel"-like approach to have this component
> configuration change reflected in all routes?
>
> Thanks for your help!
>
> Best regards,
> Atanas
>
>
>
>
>
>
>
>
> --
> View this message i
regards,
Atanas
--
View this message in context:
http://camel.465427.n5.nabble.com/How-does-a-Camel-component-update-change-existing-routes-tp5719275.html
Sent from the Camel - Users mailing list archive at Nabble.com.
