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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-4410?focusedWorklogId=879177&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-879177 ]

ASF GitHub Bot logged work on ARTEMIS-4410:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Aug/23 17:03
            Start Date: 30/Aug/23 17:03
    Worklog Time Spent: 10m 
      Work Description: gtully commented on PR #4597:
URL: https://github.com/apache/activemq-artemis/pull/4597#issuecomment-1699533685

   want to see what the test suite says and need some validation that I have not missed any countDown! will remove draft status once validate a full test suite run. but any eyes in the mean time are welcome :-)




Issue Time Tracking
-------------------

            Worklog Id:     (was: 879177)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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)