quot;)
Am I using the WireTap wrong?
Am I not creating the thread pool correctly?
thanks
ShlomiJ
--
View this message in context:
http://camel.465427.n5.nabble.com/WireTap-threads-number-keeps-on-growing-tp5557827p5557827.html
Sent from the Camel - Users mailing list archive at Nabble.com.
cess(new MyMessageSetterProcessor())
>> .wireTap("seda:wireTapQueue").onPrepare(new
>> MyCloneProcessor()).executorServiceRef(WIRETAP_THREADPOOL)
>> .log("${body}")
>
> Am I using the WireTap wrong?
> Am I not creating the thread pool correctly?
>
> thanks
>
-> CamelContext.removeRoute(String).
The last method returns true, but the wiretap threads are still alive.
I'm using Camel 2.9.0.
thanks
SJ
--
View this message in context:
http://camel.465427.n5.nabble.com/WireTap-threads-number-keeps-on-growing-tp5557827p5560267.html
Sent from the Camel - Users mailing list archive at Nabble.com.
itself.
We could possible improve this to detect in the EIPs whether the
thread pool can safely be shutdown when the route
is removed or not. I will log a JIRA about this.
> I'm using Camel 2.9.0.
> thanks
> SJ
>
> --
> View this message in context:
> http://camel.465427
en Camel is shutdown itself.
>
> We could possible improve this to detect in the EIPs whether the
> thread pool can safely be shutdown when the route
> is removed or not. I will log a JIRA about this.
>
>
>> I'm using Camel 2.9.0.
>> thanks
>> SJ
>>
sed the ThreadPoolBuilder).
In anyway, in that particular place (many quartz-routes that are removed and
created again) I switch for using multicast.
thanks for the help
SJ
--
View this message in context:
http://camel.465427.n5.nabble.com/WireTap-threads-number-keeps-on-growing-tp5557827p556105
l())/ (in case there was
> something wrong with the way I used the ThreadPoolBuilder).
>
> In anyway, in that particular place (many quartz-routes that are removed and
> created again) I switch for using multicast.
>
> thanks for the help
> SJ
>
> --
> View this message
