[
https://issues.apache.org/jira/browse/ARTEMIS-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787979#comment-17787979
]
ASF subversion and git services commented on ARTEMIS-4480:
----------------------------------------------------------
Commit 91fd12ad1f1723e4fa536d4edd9548cac2275be2 in activemq-artemis's branch
refs/heads/main from Gary Tully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=91fd12ad1f ]
ARTEMIS-4480: rationalise openwire session tx usage and operation context
usage, use completion callbacks to ensure exclusive consumers are isolated
> exclusiveConsumer release needs an operation context completion callbacks to
> ensure isolation for delivered and transacted messages
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-4480
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4480
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker, OpenWire
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> in order to see order on a queue from a consumer perspective, the consumer
> must be exclusive. Any pending work for any previous consumer, delivered put
> back on the queue or pending transaction completion rollback or commit or
> close must have occurred before dispatch to a new consumer resumes.
> The removal of the consumer must wait to release the exclusive consumer flag.
> To do this it must be able to be sure that all previous completions on the
> context are done.
> This requires consistent use of the operation context to enforce sequential
> completion.
> This problem was visible with openwire which typically has a large prefetch,
> resulting in many messages in the delivering list, moved there on rollback
> from the acks list of a transaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
