Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 24309 invoked from network); 8 Jul 2008 11:04:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jul 2008 11:04:05 -0000 Received: (qmail 40475 invoked by uid 500); 8 Jul 2008 11:04:06 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 40361 invoked by uid 500); 8 Jul 2008 11:04:06 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 40348 invoked by uid 99); 8 Jul 2008 11:04:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2008 04:04:06 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2008 11:03:13 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KGAyt-0002ct-21 for camel-user@activemq.apache.org; Tue, 08 Jul 2008 04:03:35 -0700 Message-ID: <18336673.post@talk.nabble.com> Date: Tue, 8 Jul 2008 04:03:34 -0700 (PDT) From: "S.R." To: camel-user@activemq.apache.org Subject: Camel Router is blocked when waiting for response MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: srassokhin@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org For example, I have the following route: // main route from("jms:testQueue").to("jms:someOtherQueue"); // and test consumer for "jms:someOtherQueue" from("jms:someOtherQueue").process(new Processor() { public void process(Exchange exchange) throws Exception { Thread.sleep(10000); exchange.getOut().setBody("Reply"); } }); It's easy to see that when we send request message (with JMSReplyTo field set) to the jms:testQueue, the Camel Router is blocked until reply from jms:someOtherQueue consumer is received, therefore new incoming messages can't be processed/routed during this time. Does Camel have some abilities or configuration settings to avoid this, and make this waiting asynchronous, so that other messages could be processed even if some of the previous messages hasn't been completely processed/routed yet? Thank you, Sergey -- View this message in context: http://www.nabble.com/Camel-Router-is-blocked-when-waiting-for-response-tp18336673s22882p18336673.html Sent from the Camel - Users mailing list archive at Nabble.com.