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 0161C916E for ; Mon, 18 Jun 2012 19:02:24 +0000 (UTC) Received: (qmail 10152 invoked by uid 500); 18 Jun 2012 19:02:23 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 10104 invoked by uid 500); 18 Jun 2012 19:02:23 -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 10089 invoked by uid 99); 18 Jun 2012 19:02:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 19:02:23 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of craig@mfoundry.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 19:02:17 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SghD1-0000Fu-90 for users@camel.apache.org; Mon, 18 Jun 2012 12:01:55 -0700 Date: Mon, 18 Jun 2012 12:01:55 -0700 (PDT) From: csete To: users@camel.apache.org Message-ID: <1340046115271-5714635.post@n5.nabble.com> Subject: Asynchronous behavior of SEDA queue? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm struggling to understand SEDA queue behavior in terms of asynchronous behavior. My understanding from the documentation is that if "concurrentConsumers > 1" it should spawn multiple threads to handle requests. However, it doesn't seem like this is currently working correctly and I'm sure that I'm missing something stupid. I have a route that is configured to route "seda://request_handler_tmb?concurrentConsumers=10&size=100&timeout=60000" to a handler bean. There is a single instance of that bean (if that matters). My logging shows that while the thread that does the (InOut) request handling changes from one request to the next, that there is only one outstanding request at a time. The request handling is currently wired to our test harness which is intentionally delaying responses for 20 seconds... in which case, I would expect to see multiple threads outstanding. 2012-06-18 13:44:58,070 DEBUG [ProcessorBean] (Camel (context_request_handler) thread #56 - seda://request_handler_tmb) Processing request for exchange: ID-seteramac-56604-1340045015657-5-68 2012-06-18 13:44:58,127 DEBUG [ProcessorBean] (Camel (context_request_handler) thread #56 - seda://request_handler_tmb) Successfully processed request for exchange: ID-seteramac-56604-1340045015657-5-68 2012-06-18 13:45:01,295 DEBUG [ProcessorBean] (Camel (context_request_handler) thread #53 - seda://request_handler_tmb) Processing request for exchange: ID-seteramac-56604-1340045015657-5-74 2012-06-18 13:45:01,340 DEBUG [ProcessorBean] (Camel (context_request_handler) thread #53 - seda://request_handler_tmb) Successfully processed request for exchange: ID-seteramac-56604-1340045015657-5-74 Can anyone point me in the right direction on this? I'm assuming this is something that I'm doing wrong since I can see the executor service code in the SEDA source code, but it is definitely not behaving as I would expect it to behave. Thanks, Craig -- View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-behavior-of-SEDA-queue-tp5714635.html Sent from the Camel - Users mailing list archive at Nabble.com.