Description
Given a client that is subscribed to two queues and first queue has a large message that is transferred in multiple frames, a message in the second queue can/will get the same delivery id causing a sequencing error. The cause of the bug is in proton-j and has been reported and fixed: PROTON-1892
This report is just for tracking the fix into Artemis.
Attachments
Issue Links
- relates to
-
PROTON-1892 transfers for multiplexed deliveries on the same session can have the wrong delivery-id
- Closed
-
PROTON-1901 arriving transfers for multiplexed multi-frame deliveries on a session are mishandled
- Closed
- links to