hi,
I'm having problems using the Wire Tap endpoint. *Every time a message
passes in the route, a new thread of wire tap is created, stays in "wait"
state and never dies*. Eventually my application is full of threads.
I'm creating the following ExecutorService in the registry:
ThreadPoolBuilder tpBuilder = new ThreadPoolBuilder(this.context);
> ExecutorService wiretapThreadpool =
> tpBuilder.poolSize(1).maxPoolSize(1).maxQueueSize(1).build("WireTap");
> registry.put(WIRETAP_THREADPOOL, wiretapThreadpool);
My route is simple, triggered by quartz, adds properties to the message,
wire-taps and logs:
from("quartz://myScheduler?cron=0+*+*+*+*+?")
> .process(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
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.
