Yes the default behavior shouldn't change, if anything is done it should be as an optional policy setting on the destination. Ultimately I think it would be tricky to implement with the way things currently work so I'm not sure if it will ever get implemented but a new Jira is a first start for someone to take a look at it. Matt does ask a good question though, what is the use case? Maybe there is a better way to go about trying to accomplish what you want.
On Fri, Dec 2, 2016 at 8:58 AM, Matt Pavlovich <[email protected]> wrote: > My $0.02 is that the default behavior shouldn't be changed. There is a big > benefit to being able to see the dispatched messages from a support > standpoint-- operators have the ability to view "stuck" message contents. > > I think this begs the question-- what is the use case to only see > non-dispatched messages? > > > > On 12/1/16 12:20 PM, yogu13 wrote: > >> Thanks Christopher! >> >> Does this mean a JIRA would be raised to have this implemented ? >> >> Regards, >> -Yogesh >> >> >> >> -- >> View this message in context: http://activemq.2283324.n4.nab >> ble.com/ActiveMQ-5-14-1-QueueBrowser-can-view-messages- >> being-processed-by-consumers-which-are-not-yet-unacknd- >> tp4719662p4719682.html >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> > >
