Remove the threads() as thats another EIP that also uses a thread poo..
On Thu, Jul 19, 2012 at 11:17 AM, Edwin <edwin.rabbi...@gmail.com> wrote:
> Hi Folks,
>
> I'm currently researching how to create custom thread pools for wiretap
> operations in my application.
>
> I have multiple routes and for each route I want to have an individual
> wiretap operation. The wiretap operation must run in a custom thread pool of
> poolSize & maxPoolSize of 1, maxQueueSize = unbounded
>
> I've started a couple of spikes to test my configuration however i'm
> experiencing some unexpected behaviour.
>
> When I analyse the thread pools that are getting created, I see a custom
> thread pool for each route but I also see the wiretap default thread pool
> being created for each route aswell
>
> I'm wondering is there any way of configuring the wiretap operation to use
> only the custom thread pool and not both the wiretap default thread pool and
> custom thread pool?
>
> Any insights into this issue are much appreciated
>
> Thanks,
> Edwin
>
> My configuration looks like this:
>
> ThreadPoolProfile tpProfileOne= new
> ThreadPoolProfile("tpProfileOne");
> tpProfileOne.setMaxPoolSize(1);
> tpProfileOne.setMaxQueueSize(-1);
> tpProfileOne.setPoolSize(1);
>
>
> getContext().getExecutorServiceManager().registerThreadPoolProfile(
> tpProfileOne);
>
> from("EndpointA").to(
> "EndpointB").wireTap("EndpointC").threads()
> .executorServiceRef("tpProfileOne")
> .to("EndpointD");
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Question-on-Camel-WireTap-EIP-custom-thread-pool-creation-tp5716239.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
