From ee46bd81de66e0c52be328a8070b0a87a2ad8a23 Mon Sep 17 00:00:00 2001 From: Oleg Zhurakousky Date: Mon, 29 Oct 2018 12:36:45 +0100 Subject: [PATCH] Fixed broken image links --- README.adoc | 3 +++ docs/src/main/asciidoc/overview.adoc | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/README.adoc b/README.adoc index ac0d1a9b6..066f4f669 100644 --- a/README.adoc +++ b/README.adoc @@ -67,6 +67,9 @@ You can republish a failed message after just one attempt. Starting with version 1.2, you can configure the delivery mode of republished messages. See the <>. +If the stream listener throws an `ImmediateAcknowledgeAmqpException`, the DLQ is bypassed and the message simply discarded. +Starting with version 2.1, this is true regardless of the setting of `republishToDlq`; previously it was only the case when `republishToDlq` was `false`. + IMPORTANT: Setting `requeueRejected` to `true` (with `republishToDlq=false` ) causes the message to be re-queued and redelivered continually, which is likely not what you want unless the reason for the failure is transient. In general, you should enable retry within the binder by setting `maxAttempts` to greater than one or by setting `republishToDlq` to `true`. diff --git a/docs/src/main/asciidoc/overview.adoc b/docs/src/main/asciidoc/overview.adoc index 64c461ae2..19f9d95ee 100644 --- a/docs/src/main/asciidoc/overview.adoc +++ b/docs/src/main/asciidoc/overview.adoc @@ -31,7 +31,7 @@ Alternatively, you can use the Spring Cloud Stream RabbitMQ Starter, as follows: The following simplified diagram shows how the RabbitMQ binder operates: .RabbitMQ Binder -image::rabbit-binder.png[width=300,scaledwidth="50%"] +image::{github-raw}/docs/src/main/asciidoc/images/rabbit-binder.png[width=300,scaledwidth="50%"] By default, the RabbitMQ Binder implementation maps each destination to a `TopicExchange`. For each consumer group, a `Queue` is bound to that `TopicExchange`.