On Tue, Apr 17, 2012 at 4:20 AM, mccabejj <mccab...@gmail.com> wrote: > Hello, > > Camel Version: 2.8.2 > > I am trying to setup a custom ThreadPoolProfile (Spring DSL) for the WireTap > calls in our routes. Based on the > http://camel.apache.org/threading-model.html Threading Model Documentation > it should look something like this: > > <threadPoolProfile id="customThreadPoolProfile" poolSize="10" > maxPoolSize="20" maxQueueSize="-1"/> > > And then the WireTap on the route should look something like this: > <wireTap uri="direct:gateway/services/LogRequestDesktop" > executorServiceRef="customThreadPoolProfile"/> > > However, when I define it this way in the CamelContext and fire it up, Camel > is unable to load the route due to the inability to find a threadPoolProfile > with the defined id. If I inspect/debug the running CamelContext I do not > see the custom threadPoolProfile reference. > > If I change it to the following then Camel finds the threadPoolProfile and > it works. However, this isn't really what I want since I'd like for the > custom profile to only apply for the WireTaps. > > <threadPoolProfile id="customThreadPoolProfile" poolSize="10" > maxPoolSize="20" maxQueueSize="-1" defaultProfile="true"/> > > What am I doing wrong? Thanks in advance. >
I think there was a bug in that Camel release. You may try a newer release. Or alternatively try with a <threadPool> instead of a <threadPoolProfile> and assign that to the wire tap. I think the bug was about failing to discover profiles. > JM > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/WireTap-Defining-custom-ThreadPoolProfile-tp5645423p5645423.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
