Thank you. But in my case I am sure the messages have not reached JMSExpiration date.
I assume there will be a consumer on the failover host ,once the failover happens. But when I tested, I made sure the messages will not be acknowledged . Still I see consistently the pending/enqueued messages go DLQ upon failover and don't appear in the original Queue as enqueued. Am I missing something Rajeswari -----Original Message----- From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain Sent: Wednesday, April 06, 2016 10:26 PM To: ActiveMQ Users <users@activemq.apache.org> Subject: Re: MasterSlave config ActiveMQ Only if they had reached their JMSExpiration date, or if there's a consumer on the failover host that tries and fails to consume them. Otherwise, they will continue to be available on the queue. On Wed, Apr 6, 2016 at 5:03 PM, Natarajan, Rajeswari < rajeswari.natara...@sap.com> wrote: > Hi, > > I am testing activemq master slave config using shared file system. > > 1) I issued 1 message to a queue and I saw that in both pending message > count and enqueued count. The message was not dequeued. > > 2)Killed the master ,the secondary took over ,in secondary's webconsole I > see that > > Messages dequeued as 1 > > And in the ActiveMQ.DLQ I see 1 pending message and 1 enqueued message. > > > So in case of failover ,the pending/unacknowledged messages go to DLQ and > never get processed ? > > > Thank you, > Rajeswari >
