[Jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Acknowledgment handling in the core

[<ovi...@jb...>]

anonymous wrote : 
  | That assumption is NOT correct. If the message has been NACKed it is in the queue again and can be browsed just like any other message in the queue.
  | 

JMS Specification is very vague about this:

anonymous wrote : 
  | Section 5.9
  | 
  | A client uses a QueueBrowser to look at messages on a queue without removing them. A QueueBrowser can be created from a Session or a QueueSession.
  | 
  | The browse methods return a java.util.Enumeration that is used to scan the queue?s messages. It may be an enumeration of the entire content of a queue, or it may contain only the messages matching a message selector.
  | 
  | Messages may be arriving and expiring while the scan is done. JMS does not require the content of an enumeration to be a static snapshot of queue content. Whether these changes are visible or not depends on the JMS provider.

Nowhere in this section is explicitely specified whether the "entire content of the queue" consists in messages that have not been delivered AND messages that have been delivered and NACKed, or only messages that haven't been delivered.

JBossMQ's QueueBrowsers do not return NACKed messages, only undelivered messages. 

At this point, it is not very clear to me what a browser should return, actually. We could have this as a configuration option, I believe. 



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878117#3878117

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878117