Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 41599 invoked from network); 5 Mar 2010 13:29:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Mar 2010 13:29:28 -0000 Received: (qmail 44687 invoked by uid 500); 5 Mar 2010 13:29:15 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 44655 invoked by uid 500); 5 Mar 2010 13:29:15 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 44647 invoked by uid 99); 5 Mar 2010 13:29:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Mar 2010 13:29:14 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cmoulliard@gmail.com designates 74.125.82.173 as permitted sender) Received: from [74.125.82.173] (HELO mail-wy0-f173.google.com) (74.125.82.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Mar 2010 13:29:13 +0000 Received: by wyb36 with SMTP id 36so1895196wyb.32 for ; Fri, 05 Mar 2010 05:28:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=lNqups70Sh1WQBxROiUgIsyHaCeZDNih0J5Mw4+brTI=; b=jhf/nZNnGWBRUHybrolMT8oVaj9wioZskKljgjVbYBa+v8tiAtD+LPZnvRjMEElQz1 V1Xo/k8DbebQih5fOlCwrsTGDARx+d9JAb25H0wRySCPRCziOiEPQbBvtGqiXVliXhVU cZ+rtMCi/t1M16e0Rkv6M1fp4sr1BFxrDjzeA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=vTFjhkhxzwjkgBbTCaCkXj5x69Gu6ycA9uIMBjX3QjNJL6OyGJ7Kv6We7CT7VdsMkT yODji1jeN8fc3WFxgxxioO4RxLK20iU2jLFN/P68LsXXC9PT33mQ/CutwIV7BO49cWyq xi/Pi2PnPoGJ6aMvaDmmp+uS9AFIWuDsguhKc= MIME-Version: 1.0 Received: by 10.216.85.19 with SMTP id t19mr102646wee.107.1267795732733; Fri, 05 Mar 2010 05:28:52 -0800 (PST) Date: Fri, 5 Mar 2010 14:28:52 +0100 Message-ID: Subject: Apache Camel & Durable Topic Subscription From: Charles Moulliard To: users@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 Hi, In the camel jms documentation, it is mentioned that when we would like to use Durable Topic Subscription, the limitation that we have is that we can only consume message through one JMS connection (so one thread) : "If you wish to use durable topic subscriptions, you need to specify both clientId and durableSubscriptionName. Note that the value of the clientId must be unique and can only be used by a single JMS connection instance in your entire network. You may prefer to use Virtual Topics instead to avoid this limitation. More background on durable messaging here." That means that we cannot create a camel route where we use competitor consumers (by increasing the number of threads by example) to loadbalance the messages. Is my assertion correct or my understanding of "a single JMS connection instance in your entire network" is not correct ? Kind regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com twitter : http://twitter.com/cmoulliard Linkedlin : http://www.linkedin.com/in/charlesmoulliard Apache Camel Group : http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm