GH-298: Documentation: republishToDlq is now true by default

This is the case since c2ed214df7.

A documentation update has already been done by @kinjelom in #285 but only
README.adoc was modified.
As the contents of README.adoc is generated, this correction was overridden
by d05bdc3782.

This commit modifies the source file, overview.adoc, and includes the newly
generated README.adoc file.
This commit is contained in:
Stephane Seng
2020-07-04 11:51:12 +02:00
committed by Gary Russell
parent e2ac89aadf
commit 47ae64b2d3
2 changed files with 2 additions and 2 deletions

View File

@@ -410,7 +410,7 @@ If a dead-letter queue (DLQ) is configured, RabbitMQ routes the failed message (
If set to `true`, the binder republishs failed messages to the DLQ with additional headers, including the exception message and stack trace from the cause of the final failure.
Also see the <<spring-cloud-stream-rabbit-frame-max-headroom, frameMaxHeadroom property>>.
+
Default: false
Default: `true`
singleActiveConsumer::
Set to true to set the `x-single-active-consumer` queue property to true.
+

View File

@@ -389,7 +389,7 @@ If a dead-letter queue (DLQ) is configured, RabbitMQ routes the failed message (
If set to `true`, the binder republishs failed messages to the DLQ with additional headers, including the exception message and stack trace from the cause of the final failure.
Also see the <<spring-cloud-stream-rabbit-frame-max-headroom, frameMaxHeadroom property>>.
+
Default: false
Default: `true`
singleActiveConsumer::
Set to true to set the `x-single-active-consumer` queue property to true.
+