Return-Path: 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 EC1819100 for ; Tue, 14 Feb 2012 14:26:48 +0000 (UTC) Received: (qmail 66025 invoked by uid 500); 14 Feb 2012 14:26:48 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 65999 invoked by uid 500); 14 Feb 2012 14:26:48 -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 Delivered-To: moderator for users@camel.apache.org Received: (qmail 56670 invoked by uid 99); 14 Feb 2012 14:23:42 -0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted nor denied by domain of shlomijava@gmail.com) Date: Tue, 14 Feb 2012 06:23:17 -0800 (PST) From: ShlomiJ To: users@camel.apache.org Message-ID: <1329229397038-5482568.post@n5.nabble.com> In-Reply-To: <4F3A5883.4030204@gmail.com> References: <4F3A5883.4030204@gmail.com> Subject: Re: Threads not consuming in parallel MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_48774_29243089.1329229397040" ------=_Part_48774_29243089.1329229397040 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit *Solved!* sort of... The problem was that the JMS queue got filled with messages *before* any consumer was available. When the consumers were finally started, by initiating the to:activemq endpoint, all existing messages in the JMS queue were assigned to a *single consumer!* That caused the _appearance_ of a sequential processing, while actually *new* messages WERE distributed among consumers evenly and were passed in parallel, each to a different thread in the pool. to Willem.Jiang: Willem.Jiang wrote > Did you have a change to set the activemq endpoint option of > concurrentConsumers like this? > > I've tried it, but it simply overrides the corresponding JmsConfiguration's properties from the camel-context.xml. It did not changed anything. Now I realize that a consumer is attached to a thread from the pool, until that thread is finished. Why? *Can't a consumer simply pass a message to a thread from the pool and be done with it, without having to wait for the thread to finish it run?* any thoughts? ShlomiJ -- View this message in context: http://camel.465427.n5.nabble.com/Threads-not-consuming-in-parallel-tp5482274p5482568.html Sent from the Camel - Users mailing list archive at Nabble.com. ------=_Part_48774_29243089.1329229397040--