[activemq-website] branch main updated: [AMQ-8440] Update for sendDuplicateFromSToreToDLQ flag

[jb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jbonofre pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 87f3b43c9 [AMQ-8440] Update for sendDuplicateFromSToreToDLQ flag
     new 718a96ca8 Merge pull request #79 from mattrpav/AMQ-8440
87f3b43c9 is described below

commit 87f3b43c9f6e571e62ff4ebe86df425ef8ed7e60
Author: Matt Pavlovich <ma...@hyte.io>
AuthorDate: Thu Feb 24 08:36:50 2022 -0600

    [AMQ-8440] Update for sendDuplicateFromSToreToDLQ flag
---
 src/per-destination-policies.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/per-destination-policies.md b/src/per-destination-policies.md
index 9c8d02f17..6aee3b369 100644
--- a/src/per-destination-policies.md
+++ b/src/per-destination-policies.md
@@ -33,6 +33,7 @@ Common Property|Default|Description
 `storeUsageHighWaterMark`|`100`|The percentage (%) threshold of the `<systemUsage>/<storeUsage>` store limit which when exceeded causes a producer send to block.
 `useCache`|`true`|If `true` persistent messages are cached for fast retrieval from store.
 `usePrefetchExtension`  |`true`|The prefetch extension is used when a message is delivered but not ACK'ed, such that the broker can dispatch another message, e.g., `prefetch == 0`, the idea being that there will always be prefetch number of messages pending. It also allows a transaction batch to exceed the prefetch value.
+`sendDuplicateFromStoreToDLQ` |`false`|(v5.17.0) If `true`, will send a copy of message to DLQ when duplicateFromStore condition is detected. Before v5.17.0, the default behavior was `true`
 `sendFailIfNoSpace`|`false`|(v5.16.0) If `true`, will cause a send to fail with a `javax.jms.ResourceAllocationException` when the destination has reached is resource limits (memory or storage)
 `sendFailIfNoSpaceAfterTimeout`|`0`|(v5.16.0) If `> 0`, will cause a send to fail with a `javax.jms.ResourceAllocationException` when the destination resource limits (memory or storage) remain exhausted for the configured duration in milliseconds