That's great news that it's reproducible, because that means you can set it up in a test environment and attach a debugger to see what's happening and why. I'd recommend setting a breakpoint on http://activemq.apache.org/maven/5.12.0/apidocs/org/apache/activemq/store/jdbc/adapter/DefaultJDBCAdapter.html#doSetLastAck(org.apache.activemq.store.jdbc.TransactionContext,%20org.apache.activemq.command.ActiveMQDestination,%20org.apache.activemq.command.XATransactionId,%20java.lang.String,%20java.lang.String,%20long,%20long) to start.
Tim On May 5, 2017 7:24 AM, "khandelwalanuj" <anuj.cool.khandel...@gmail.com> wrote: > No. There is only one durable subscriber, I have verified it. > > This is happening everytime, it's reproducible. > > More details: > > 1. 1 producer 1 durable subscriber. Subscriber is in auto_ack mode. > 2. Producer sent 100 persistent messages to consumer > 3. Consumer successfully consumed them. > 4. DB still has those messages. > 5. Stop producer and consumer both, but messages are still there. > 6. Even after restarting broker, message does not get deleted. > > Thanks, > Anuj > > > > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/ActiveMQ-with-PostgreSQL-Not-deleting- > persistent-messages-sent-to-a-topic-tp4725654p4725661.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
