From 8b61bc8706c1f55439c62fe1e8861d647316d0b1 Mon Sep 17 00:00:00 2001 From: Maciej Walkowiak Date: Sat, 9 Mar 2019 20:29:30 +0100 Subject: [PATCH] Fix documentation link to Error Handling in Spring Cloud Stream Binder Resolves #198 --- docs/src/main/asciidoc/overview.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/overview.adoc b/docs/src/main/asciidoc/overview.adoc index 14410e9cd..a02a483dd 100644 --- a/docs/src/main/asciidoc/overview.adoc +++ b/docs/src/main/asciidoc/overview.adoc @@ -637,7 +637,7 @@ Notice that the count property in the `x-death` header is a `Long`. == Error Channels Starting with version 1.3, the binder unconditionally sends exceptions to an error channel for each consumer destination and can also be configured to send async producer send failures to an error channel. -See "`<>`" for more information. +See "`<>`" for more information. RabbitMQ has two types of send failures: @@ -647,7 +647,7 @@ RabbitMQ has two types of send failures: The latter is rare. According to the RabbitMQ documentation "[A nack] will only be delivered if an internal error occurs in the Erlang process responsible for a queue.". -As well as enabling producer error channels (as described in "`<>`"), the RabbitMQ binder only sends messages to the channels if the connection factory is appropriately configured, as follows: +As well as enabling producer error channels (as described in "`<>`"), the RabbitMQ binder only sends messages to the channels if the connection factory is appropriately configured, as follows: * `ccf.setPublisherConfirms(true);` * `ccf.setPublisherReturns(true);`