I thought the whole point of QueueBrowser was to allow browsing (not consuming) messages. Am I wrong to think that failure to mark messages as consumed from a QueueBrowser is correct and expected behavior?
Why aren't you letting it fail delivery and get moved to the DLQ so the next message can be processed? That's why that feature is built into the broker, after all. On Jun 8, 2015 12:07 PM, "bhavin.patel" <bhavin.pa...@rockshore.net> wrote: > Hi Tim, > > Thanks for reply. > > My session transacted is set to FALSE. > I have tried with that as TRUE and commit session but even that didn't > work. > > I'm running out of ideas. > > Bhavin > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Can-not-remove-message-from-Queue-tp4697351p4697388.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
