[
https://issues.apache.org/jira/browse/ARTEMIS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762763#comment-17762763
]
ASF subversion and git services commented on ARTEMIS-4418:
----------------------------------------------------------
Commit 91debf25dbf0f3924d511ee615c6f9b0545e2a5f in activemq-artemis's branch
refs/heads/main from Gary Tully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=91debf25db ]
ARTEMIS-4418 use consumer delivery sequence in messageId for openwire broker
sequence id, makes delivery count calculation independent of message order
> openwire lastDeliveredSequenceId depends on message order, it should not
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-4418
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4418
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.30.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
>
> Following up on ARTEMIS-4410, message order is necessary to make sense of the
> openwire consumer close lastDeliveredSequence id, when order is compromised
> the delivery count on prefetched messages can get incremented in error.
> The root cause is the use of the persistence id, or store order, which is
> itself loose. It would be better if the sequence id was directly related to
> the consumer delivered list and independent of total queue order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
