[jira] [Resolved] (ARTEMIS-4410) Openwire prefetched messages can be out of order after failover to an exclusive queue

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

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

Robbie Gemmell resolved ARTEMIS-4410.
-------------------------------------
    Resolution: Fixed

> Openwire prefetched messages can be out of order after failover to an exclusive queue
> -------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4410
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4410
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: OpenWire
>    Affects Versions: 2.30.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 2.31.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> related to ARTEMIS-4284 but when the connection drops, and the client reconnects. Any inflight messages can be addSorted to the queue, but any new consumer on a newly created connection can see the queue without certainty that prefetched are added back.
> with an exclusive queue, the order should be preserved for each successive exclusive consumer.
> The default prefetch means this is typical  with openwire, but the visibility of delivered messages is not unique to that protocol. With any unacked messages that exceed credit this can occur in the event of unclean disconnect and reconnect.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)