Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.6.3, 2.9.0
-
None
-
None
Description
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):
$ ./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)}
Ideally, with a single consumer like this, the order would be preserved.
Attachments
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
ARTEMIS-2458 AMQP Transaction rollback causes loss of message order
-
- Closed
-