I tried to reproduce the error as you said.
But when I update the bundle, the alive thread number doesn't increase,
and there is no other thread which name is start with timer://xxx.
I also checked the camel timer component, if the timer component is
stopped, camel will cancel the timer, and the timer thread will be
destroyed.
When you update the bundle, the camel context will be stopped and new
camel context will be started.
Willem
marcin80 wrote:
Hi,
I'm using Camel 1.6 with ServiceMix4 (FuseESB). I have an OSGi bundle
containing camel route whitch starts with:
from("timer:foo?period=5000")....
I'm using jconsole and I can see there is one thread for this timer. But,
when I update a bundle new thread is created for my timer and old thread
isn't destroyed.
There is any option to destoy old thread when I update bundle?
Cheers,
Marcin
