Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 29123 invoked from network); 30 Nov 2010 20:40:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Nov 2010 20:40:45 -0000 Received: (qmail 4560 invoked by uid 500); 30 Nov 2010 20:40:45 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 4524 invoked by uid 500); 30 Nov 2010 20:40:45 -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 4516 invoked by uid 99); 30 Nov 2010 20:40:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Nov 2010 20:40:45 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Nov 2010 20:40:40 +0000 Received: from sam.nabble.com ([192.168.236.26]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1PNWzq-0003hf-M9 for users@camel.apache.org; Tue, 30 Nov 2010 12:40:18 -0800 Date: Tue, 30 Nov 2010 12:40:18 -0800 (PST) From: khein To: users@camel.apache.org Message-ID: <1291149618670-3286723.post@n5.nabble.com> In-Reply-To: References: <1291070515340-3285351.post@n5.nabble.com> Subject: Re: concurrentConsumers issue MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've used the Spring JMS listeners many times and never encountered this. I'll convert my test to using Spring JMS to verify. This is major issue because of the unreliability it causes. Basically a long running thread (or one that transactionally binds, hangs, etc) delays processing of other downstream messages. In a 4 consumer pool, if the 1st message receives causes long processing, it delays the 5th, 9th, 13th message, while the others process in a more timely manner. -- View this message in context: http://camel.465427.n5.nabble.com/concurrentConsumers-issue-tp3285351p3286723.html Sent from the Camel - Users mailing list archive at Nabble.com.