Return-Path: 
 <users-return-28465-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4FB5C9D09
	for <apmail-camel-users-archive@www.apache.org>;
 Tue, 17 Apr 2012 03:32:16 +0000 (UTC)
Received: (qmail 40744 invoked by uid 500); 17 Apr 2012 03:32:14 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 40643 invoked by uid 500); 17 Apr 2012 03:32:14 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 40289 invoked by uid 99); 17 Apr 2012 03:32:13 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 03:32:13 +0000
X-ASF-Spam-Status: No, hits=0.6 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.217.173 as permitted sender)
Received: from [209.85.217.173] (HELO mail-lb0-f173.google.com)
 (209.85.217.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 03:32:06 +0000
Received: by lboi15 with SMTP id i15so992582lbo.32
        for <users@camel.apache.org>; Mon, 16 Apr 2012 20:31:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        bh=vtPvVB0EN/V9TgxRmO4KlplXeamH9iYW2kL+sHaEqek=;
        b=uG2MvdfUwx8HG9JCZbVcIzrD+oF722l4SHXQSAyOwrx9+SDMZLkaj7ONVCYF0emf51
         BUzmGurqU5Oh/Td/Cw9AaQYBEOJsaB/IuXPFQ6IitqmLe/flqoUXG3eK+3sZ6h6ocX1k
         096KePABx1vPovxZ7IX0UzvZzAuJW+TWx1BtrcP6wLwnrAHaj158RHao8TmhD8+X2rlI
         Q+4ZYIzsJWN26zW0Fze1EYV8BrSzvCyaOxOvQ3Lq4yQub8zMxtAX2PbF28sGOSNNHkph
         HC3kv5oTcEBKj3aHasHH+04mJZ4nupZxxqx+22Lfd7qtDY4E9IXo4BOiqX5XTa5OwfO0
         QlqA==
Received: by 10.112.98.70 with SMTP id eg6mr1994654lbb.13.1334633505251; Mon,
 16 Apr 2012 20:31:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.75.130 with HTTP; Mon, 16 Apr 2012 20:31:24 -0700 (PDT)
In-Reply-To: <1334629202251-5645423.post@n5.nabble.com>
References: <1334629202251-5645423.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 17 Apr 2012 05:31:24 +0200
Message-ID: 
 <CAGB5yNnJi4aixayaRqM3gcNYq68k_cUy42oNVJ30O+_FaJ8f9w@mail.gmail.com>
Subject: Re: WireTap - Defining custom ThreadPoolProfile
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 17, 2012 at 4:20 AM, mccabejj <mccabejj@gmail.com> wrote:
> Hello,
>
> Camel Version: 2.8.2
>
> I am trying to setup a custom ThreadPoolProfile (Spring DSL) for the Wire=
Tap
> calls in our routes. =A0Based on the
> http://camel.apache.org/threading-model.html Threading Model Documentatio=
n
> it should look something like this:
>
> <threadPoolProfile id=3D"customThreadPoolProfile" poolSize=3D"10"
> maxPoolSize=3D"20" maxQueueSize=3D"-1"/>
>
> And then the WireTap on the route should look something like this:
> <wireTap uri=3D"direct:gateway/services/LogRequestDesktop"
> executorServiceRef=3D"customThreadPoolProfile"/>
>
> However, when I define it this way in the CamelContext and fire it up, Ca=
mel
> is unable to load the route due to the inability to find a threadPoolProf=
ile
> with the defined id. =A0If 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 an=
d
> it works. =A0However, this isn't really what I want since I'd like for th=
e
> custom profile to only apply for the WireTaps.
>
> <threadPoolProfile id=3D"customThreadPoolProfile" poolSize=3D"10"
> maxPoolSize=3D"20" maxQueueSize=3D"-1" defaultProfile=3D"true"/>
>
> What am I doing wrong? =A0Thanks 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-D=
efining-custom-ThreadPoolProfile-tp5645423p5645423.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



--=20
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/