[ https://issues.apache.org/jira/browse/ARTEMIS-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790769#comment-17790769 ]
ASF subversion and git services commented on ARTEMIS-4517: ---------------------------------------------------------- Commit fed01276baa5646d52968d7a2a897462c6faa7cd in activemq-artemis's branch refs/heads/main from Gary Tully [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=fed01276ba ] ARTEMIS-4517 - cancel message references in queue sequence order > rollback causes loss of message order if concurrent producers commit out of > order > ---------------------------------------------------------------------------------- > > Key: ARTEMIS-4517 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4517 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 2.31.0 > Reporter: Gary Tully > Assignee: Gary Tully > Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > As part of ARTEMIS-2458, cancel puts messages back onto the queue on sequence > id order, but the sequence id is allocated to producers on message send (via > the message store) and can be unordered w.r.t to a queue view when producer > transactions overlap. > The queue has the correct initial producer order, with out of order > sequenceId. > When messages are cancelled back to the queue they go back in sqeuenceId > order in error, giving a consumer out of order messages on the second or > subsequent delivery attempts. > > each queue needs to retain its own sequence and apply to its reference, such > that messages can be cancelled back and retain the queue order. -- This message was sent by Atlassian Jira (v8.20.10#820010)