[
https://issues.apache.org/activemq/browse/AMQNET-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56161#action_56161
]
Palm Kevin commented on AMQNET-206:
-----------------------------------
After some research on the web, it seems that your implmentation is right.
QueueBrowser does never remove messages from queue.
So, I guess the best method to acknowledge messages is to store their
JMSMessageId's while browsing and "consume" them with a MessageConsumer in a
second round... Or does anybody knows a better way of achieving this (Because
with that solution all messages to be acknowledged are downloaded twice...)?
> Added QueueBrowser implementation for ActiveMQ.
> -----------------------------------------------
>
> Key: AMQNET-206
> URL: https://issues.apache.org/activemq/browse/AMQNET-206
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.2.0
> Reporter: Symon Rottem
> Assignee: Jim Gomes
> Fix For: 1.3.0
>
> Attachments: Apache.NMS.ActiveMQ_Browser.patch
>
>
> I've ported the code for the QueueBrowser as best I could from the JMS
> implementation. I've also ported the unit tests for the new class and they
> appear to pass. Please note that I'm a complete newbie to NMS and I'm not
> sure that I've done things "just right" so it's probably a good idea if
> someone reviews the patch to be safe.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
