[
https://issues.apache.org/jira/browse/ARTEMIS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-4418:
--------------------------------
Description:
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.
was:
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.
We should use the default (core) delivery semantics of treating credit or
delivered or prefetched messages as not delivered on non exclusive queues.
Only on an exclusive queue will we respect the lastDeliveredSequenceId
> 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)
