camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hartmut Lang <>
Subject RE: SedaConsumer not removed on endpoint remove
Date Mon, 12 Mar 2012 10:44:57 GMT
Good news!
Is there a ticket-number for this?

-----Original Message-----
From: Claus Ibsen [] 
Sent: Montag, 12. März 2012 11:39
Subject: Re: SedaConsumer not removed on endpoint remove

On Mon, Mar 12, 2012 at 11:33 AM, Hartmut Lang <> 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
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message