qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-3530) Unify the QueueBrowsers behavior on 0-8/0-9/0-10 code paths when failover happens.
Date Fri, 18 Jul 2014 23:08:05 GMT

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

Keith Wall resolved QPID-3530.
------------------------------

    Resolution: Fixed

Agreed in a product backlog review - won’t fix.

> Unify the QueueBrowsers behavior on  0-8/0-9/0-10 code paths when failover happens.
> -----------------------------------------------------------------------------------
>
>                 Key: QPID-3530
>                 URL: https://issues.apache.org/jira/browse/QPID-3530
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Alex Rudyy
>              Labels: browsing, failover
>             Fix For: Future
>
>
> The current functionality of QueueBrowser on 0-8/0-9/0-10 code paths behaves differently
when failover happens. QueueBrowsers on 0-10 path invoke receiveNoWait() in order to browse
the queue while QueueBrowsers on 0-9 path invoke receive() method. When failover happens 0-8/0-9/0-9-1
QueueBrowsers block and restart the browsing of the queue from the beginning after failover
is finished while 0-10 QueueBrowsers return null when invoked during failover. 
> QueueBrowser functionality should be changed to throw NoSuchElementException on iteration
through the queue messages when falover happens.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message