[
https://issues.apache.org/jira/browse/ARTEMIS-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724202#comment-17724202
]
Gary Tully commented on ARTEMIS-4285:
-------------------------------------
It may make sense to do this just on the increment from 0->1 to support a
persistent redelivery flag. That is what we did in 5.x to avoid too much
overhead but still be usefull.
see:
https://issues.apache.org/jira/browse/AMQ-5068?focusedCommentId=13947821&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13947821
> Disable Redelivery Persistence for new broker installations.
> ------------------------------------------------------------
>
> Key: ARTEMIS-4285
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4285
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Clebert Suconic
> Priority: Major
>
> We should allow disabling persisted redelivery on messages.
> Every time a message is redelivery, and scheduled redelivery is used, an
> update record is stored in the broker.
> This may add a big burden in the journal or jdbc journal.
> We will keep this as true by default (in java) however new broker.xml
> configuration will have this as false, so we will keep current users'
> expectation while setting this to false for any new broker installation.
> This is a borderline between bug and improvement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
