[
https://issues.apache.org/jira/browse/ARTEMIS-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937499#comment-16937499
]
Keith Wall commented on ARTEMIS-2161:
-------------------------------------
[~robbie] [~gsim] [~clebertsuconic] I tested 2.10 with Gordon's attached
reproducer (release.py). I agree it looks like this issue is fixed.
> [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
> Reporter: Gordon Sim
> Priority: Major
> 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)
