[
https://issues.apache.org/jira/browse/ARTEMIS-3093?focusedWorklogId=555940&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-555940
]
ASF GitHub Bot logged work on ARTEMIS-3093:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Feb/21 18:27
Start Date: 22/Feb/21 18:27
Worklog Time Spent: 10m
Work Description: michaelandrepearce edited a comment on pull request
#3463:
URL: https://github.com/apache/activemq-artemis/pull/3463#issuecomment-783575301
Im getting a bit of de ja vu here. Didnt alot of these changes being removed
you/we added for something similar with ordering before on amqp? In Artemis-2458
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 555940)
Time Spent: 40m (was: 0.5h)
> Message Order broken with Core Protocol when rolling back transactions
> ----------------------------------------------------------------------
>
> Key: ARTEMIS-3093
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3093
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.16.0
> Reporter: John Behm
> Assignee: Clebert Suconic
> Priority: Critical
> Labels: artemis, bug, order, queue
> Fix For: 2.18.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ARTEMIS-2458
> This issue still persists.
>
> Consuming from a queue with two threads with distinct sessions while rolling
> back directly in each thread when receiving a message breaks the whole order
> of the queue. Even with delays of 500ms.
> The queue/addresse is configured as ANYCAST queue.
>
> (In 2.10 this issue persists as well.)
> Basic Test setup is like this:
> You have a non-clustered single instance of Artemis.
> You do have a redelivery-delay of 0.
> You fill an anycast queue with 1000/10000 ordered messages.
> You disconnect your producer and start the two or more consumers that try to
> fetch all of the messages from that exact same queue, but can only get one,
> as you always roll back the session.
> Each time any of those two(or more) consumers receives a message, they
> rollback the session instantly and sleep 0 to 500 ms.
> After rolling back every time you receive a message on any of your consumer
> threads, you expect to always get the message with the content "0".
> After like ten iterations of this ping-pong rollback between your two
> consumer threads, you start to get completely random messages, not even
> within the range of 0 through 10, but completely arbitrary ones from within
> the queue.
> You disconnect your consumers and try dumping the queue. You get a completely
> unordered message queue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
