On Mon, Mar 12, 2012 at 11:33 AM, Hartmut Lang
<hartmut.l...@ericsson.com> wrote:
> 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?
>
Its fixed in the next release.
> /Hartmut
>
--
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/
