You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Updated) (JIRA)" <ji...@apache.org> on 2011/10/07 13:02:29 UTC
[jira] [Updated] (QPID-3530) Unify the QueueBrowsers behavior on
0-8/0-9/0-10 code paths when failover happens.
[ https://issues.apache.org/jira/browse/QPID-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-3530:
-----------------------------
Description:
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.
was:
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-9 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.
Summary: Unify the QueueBrowsers behavior on 0-8/0-9/0-10 code paths when failover happens. (was: Unify the QueueBrowsers behvaiours on 0-8/0-9/0-10 code paths when failover happens.)
> 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
> Fix For: 0.13
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org