The odds of that bug being prioritized for work will increase if you can use a debugger to help figure out specifically what is failing in the code. Nothing says that one of the developers won't prioritize it as-is, but your odds would be better if you were able to say "here's the block of code with the wrong logic."
But it's really your decision how important it is to you that the bug get fixed as soon as possible. Tim On May 8, 2017 1:27 AM, "khandelwalanuj" <[email protected]> wrote: > I think doSetLaskAck is working fine perfectly as I can see that the value > of > last ackd message is getting updated properly. > > I have logged a bug request https://issues.apache.org/ > jira/browse/AMQ-6671 > for the same. > > Thanks, > Anuj > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/ActiveMQ-with-PostgreSQL-Not-deleting- > persistent-messages-sent-to-a-topic-tp4725654p4725733.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
