On Wed, Jul 6, 2011 at 3:15 PM, Daniel Spaven <danspa...@gmail.com> wrote: > Hi, > > I've been having some problems removing routes programmatically. My routes > use camels CBR pattern to route JMS messages. I remove them using the code: > > context.stopRoute(routeIDString); > context.removeRoute(routeIDString); > > Now the problem is not that the route is not removed it is, but that it > appears to stop other routes in the same camel context from working. > > Now I've tested it using the following camel-core and camel-jms versions: > > 2.5.0 - Works > 2.6.0 - Works > 2.7.0 - Fails: Existing routes don't work after a route is removed. However > new routes added will still work. JMS consumer for old unremoved routes > still active but messages never get consumed. The route state from JMX of > the not working routes are still "Started" > 2.7.1 - Fails in same way > 2.7.2 - Fails in same way > > N:B Stopping and starting the same route seems to work fine. It's when a > route is stopped and then removed that the problems appear to occur. > > Any ideas? user error or bug? >
Can you post your route that is causing the trouble for you? I cannot reproduce the issue with 2 routes using seda endpoints on trunk. > Cheers, > > Dan > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
