I am trying to understand, sorry if I sound , I don't believe you or skeptic. I have an application with the broker url defined as below (with shared file system)
failover:(tcp://<hostname1>:61616,tcp://<hostname2>:61616. When I failover I see the web console and see one consumer on the fail over host ,as the application is having a consumer and got a message ,but did not acknowledge (delaying it on purpose for a use case) during failover.. In our use case, there will be messagse sent to the queue and we do some processing ,but not acknowledging the messages ,unless we get a condition satisfied ,which might take some time. So when a failover happens within that time ,all such messages will be moved to DLQ? Is there any way to have them in the same state as before in the fail over host. Thank you, Rajeswari -----Original Message----- From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain Sent: Thursday, April 07, 2016 5:41 AM To: ActiveMQ Users <users@activemq.apache.org> Subject: RE: MasterSlave config ActiveMQ Quoting from what I originally wrote you: "or if there's a consumer on the failover host that tries and fails to consume them." Consuming a message but not acking it == failing to consume it. The failover functionality works, despite your apparent skepticism; retry your test with no consumers if you don't believe me. Tim On Apr 7, 2016 5:22 AM, "Natarajan, Rajeswari" <rajeswari.natara...@sap.com> wrote: > FYI using non-transactional session with > ActiveMQSession.INDIVIDUAL_ACKNOWLEDGE > > Rajeswari > > -----Original Message----- > From: Natarajan, Rajeswari [mailto:rajeswari.natara...@sap.com] > Sent: Thursday, April 07, 2016 3:57 AM > To: users@activemq.apache.org > Subject: RE: MasterSlave config ActiveMQ > > 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 > > >
