My scenario is to dynamically add and remove routes through some kind of
registration-service.
My routes have a seda input like:
from("seda://seda-id").to("http://hostame";)
Now the problem is, that if i remove the route and endpoints during runtime,
the related "SedaConsumer" threadpool stays alive.
And when i dynamically create the same route again, an additional
"SedaConsumer" is created.
So i somehow have more and more "SedaConsumer" pools in my context.
Any ideas how to deal with that?
/Hartmut
