Looks right to me. You could test it manually too by simply shutting app2 down and see what happens ;)
Consider using the exponential backoff setting. It's handy where network problems might occur http://activemq.apache.org/camel/dead-letter-channel.html. pratibhaG wrote: > > Suppose I am sending a message from app1 to app2. > If app2 is down, at servicemix logs I get java.net.ConnectException. > > I think if I am using deadletter the error should be caught and after some > retries it should be given to dead letter channel. > Here is the configuration: > > errorHandler(deadLetterChannel( > > "jbi:service:http://servicemix.in2m.com/samples/http/JMSServiceCamelErrorHandler";).maximumRedeliveries(2)); > > from("jbi:service:http://servicemix.in2m.com/samples/http/httpConsumer";) > > .to("jbi:service:http://servicemix.in2m.com/samples/http/MyProviderService";); > > So if i am not able to connect to my "MyProviderService", my message > should be sent to "JMSServiceCamelErrorHandler" right? > > Or my understanding is wrong? > > Pratibha > -- View this message in context: http://www.nabble.com/How-does-camel-dead-letter-channel-work--tp18026494s22882p18055736.html Sent from the Camel - Users mailing list archive at Nabble.com.
