Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 88824 invoked from network); 24 Jun 2008 11:01:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Jun 2008 11:01:16 -0000 Received: (qmail 94704 invoked by uid 500); 24 Jun 2008 11:01:18 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 94684 invoked by uid 500); 24 Jun 2008 11:01:18 -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 94673 invoked by uid 99); 24 Jun 2008 11:01:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jun 2008 04:01:18 -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, 24 Jun 2008 11:00:26 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KB6GS-00032N-RM for camel-user@activemq.apache.org; Tue, 24 Jun 2008 04:00:44 -0700 Message-ID: <18088649.post@talk.nabble.com> Date: Tue, 24 Jun 2008 04:00:44 -0700 (PDT) From: pratibhaG To: camel-user@activemq.apache.org Subject: Re: How does camel dead letter channel work? In-Reply-To: <18085349.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: pratibha.ghogale@in2m.com References: <18026494.post@talk.nabble.com> <18055736.post@talk.nabble.com> <18064642.post@talk.nabble.com> <485F5E21.50407@skynet.be> <18084684.post@talk.nabble.com> <18085026.post@talk.nabble.com> <18085349.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Now I have following configuration: public void configure() { errorHandler(deadLetterChannel( "jbi:service:http://servicemix.in2m.com/samples/http/JMSServiceCamelErrorHandler?mep=in-only") .maximumRedeliveries(4).initialRedeliveryDelay(300000).backOffMultiplier(2.0)); from("jbi:service:http://servicemix.in2m.com/samples/http/httpConsumer") .to("jbi:service:http://servicemix.in2m.com/samples/http/MyProviderService") .to("jbi:service:http://servicemix.in2m.com/samples/http/bean2Service"); } I think the flow should be like this: 1)message is consumed from httpConsumer. 2)messge is sent to MyProviderService. 3)If MyProviderService is up and running, everything goes fine and the message is sent to bean2 service. 4)If MyProviderService is down, the messsage will be redelivered after 300000 ms that is 5 minutes. After 5 minutes if the application is again down, message will be redelivered after 10 minutes, then after 20 minutes and then 40 minutes. If still MyProviderService is not up, message will be sent to deadletterchannel. But I am getting something different: After first attempt as per my servicemix logs it wits for 300000 ms, but then I get java.lang.IllegalStateException: Exchange not found Also if my client's request time is 2008-06-24 16:11:41,112, then it gets response at 2008-06-24 16:12:51,125. What should ideally happen? Pratibha -- View this message in context: http://www.nabble.com/How-does-camel-dead-letter-channel-work--tp18026494s22882p18088649.html Sent from the Camel - Users mailing list archive at Nabble.com.