Hi Jakub, Yes, from the queue on the broker. As far as the broker is concerned, it remains "in-flight" permanently. What's weirder is when I run a standalone java client to consume the messages, it has no trouble whatsoever. So I think there's something going on in the client side that's causing messages not to be acknowledged.
I have a manager class that is responsible for consuming & publishing to the topic. The same manager class is responsible for consuming messages from the queue. I have two nested listener classes which are instantiated as member variables of the manager class in the constructor. I don't necessarily care about sequence; more that there is only ever one message for a given id being processed at any given moment. Would message groups still apply? Thanks, Matt On Thu, Feb 23, 2012 at 9:41 AM, Jakub Korab <jakub.ko...@gmail.com> wrote: > Hi Matt, > > When you say that the message is not being dequeued, do you mean from the > queue on the broker? > > The overall scheme itself seems to be pretty complicated; where are the > topic messages coming from? > > If you are trying to ensure that messages for a particular id are consumed > in sequence then perhaps message groups > (http://activemq.apache.org/message-groups.html) might fit the bill better > and simplify your code. > > Jakub > >
