[jira] [Updated] (ARTEMIS-384) Different QueueBrowser Behavior

["Justin Bertram (JIRA)" <ji...@apache.org>]

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

Justin Bertram updated ARTEMIS-384:
-----------------------------------
    Fix Version/s:     (was: 1.2.0)

> Different QueueBrowser Behavior
> -------------------------------
>
>                 Key: ARTEMIS-384
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-384
>             Project: ActiveMQ Artemis
>          Issue Type: Sub-task
>          Components: OpenWire
>    Affects Versions: 1.1.0
>            Reporter: Howard Gao
>            Priority: Minor
>
> Openwire (ActiveMQ5.x) clients can have a queue browser that can see messages in delivering state. For exmaple a queue "Test" has one normal consumer and a queue browser. If we send 4 messages to the queue, those are delivered to consumer (not acked). When the queue browser tries to browse the queue, it will see all 4 messages even they are in delivering state.
> Currently artemis won't be able to do that because those messages are not in the queue's iterator.
> See test org.apache.activemq.broker.BrokerTest#testQueueBrowserWith2Consumers()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)