[
https://issues.apache.org/jira/browse/ARTEMIS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762685#comment-17762685
]
Gary Tully commented on ARTEMIS-4418:
-------------------------------------
for reference, the lastDeliveredSequenceId being used on the client:
https://github.com/apache/activemq/blob/fc13d61714c1554433fd06becceed55dbe9ef8e5/activemq-client/src/main/java/org/apache/activemq/ActiveMQMessageConsumer.java#L932
> 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)
