You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2021/02/03 11:55:00 UTC

[jira] [Commented] (ARTEMIS-3093) Message Order broken with Core Protocol when rolling back transactions

    [ https://issues.apache.org/jira/browse/ARTEMIS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277939#comment-17277939 ] 

Robbie Gemmell commented on ARTEMIS-3093:
-----------------------------------------

Though it may be related in overall effect, I don't believe this is ARTEMIS-2458 (/ARTEMIS-2161) persisting. The usage described here is for a different protocol with another client, plus a different overall scenario through being about multiple consumers.

 

It would help someone else looking later if you could more specifically describe the behaviour it is you actually see, and what it is you expected instead. Perhaps provide a reproducer too.

> 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
>            Reporter: John Behm
>            Priority: Critical
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)