[jira] [Closed] (ARTEMIS-2161) [AMQP] released messages lose order

["Robbie Gemmell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell closed ARTEMIS-2161.
-----------------------------------
    Resolution: Fixed

Based on that I've just marked it resolved in 2.10.0. Can reopen if needed.

> [AMQP] released messages lose order
> -----------------------------------
>
>                 Key: ARTEMIS-2161
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2161
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.6.3, 2.9.0
>            Reporter: Gordon Sim
>            Priority: Major
>             Fix For: 2.10.0
>
>         Attachments: release.py
>
>
> If messages are explicitly released, they lose their original ordering. (Implicit release by ending session without acknowledging seems *not* to have the same effect).
> E.g. using proton python examples (with queue named 'examples' created, else use -a option below):
> {noformat}
> $ ./simple_send.py -m 20
> all messages confirmed
> $ ./simple_recv.py -m 5
> {u'sequence': int32(1)}
> {u'sequence': int32(2)}
> {u'sequence': int32(3)}
> {u'sequence': int32(4)}
> {u'sequence': int32(5)}
> $ ./simple_recv.py -m 5
> {u'sequence': int32(11)}
> {u'sequence': int32(10)}
> {u'sequence': int32(9)}
> {u'sequence': int32(8)}
> {u'sequence': int32(7)}
> $ ./simple_recv.py -m 5
> {u'sequence': int32(16)}
> {u'sequence': int32(15)}
> {u'sequence': int32(14)}
> {u'sequence': int32(13)}
> {u'sequence': int32(12)}
> {noformat}
> Ideally, with a single consumer like this, the order would be preserved.



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