What's message ack mode you're using? If your consumer does not acknowledge messages that have been processed, eg, you may forget to manual ack message when using client ack mode or forget to commit session when using transaction, those messages will be redelivered when consumer or broker gets restarted.
2014-02-20 11:24 GMT+08:00 ramdassv <rvenkadasw...@apptivo.net>: > Hi Torsten, > > Thanks for your response. Yes I have both the broker instances work on the > same levelDB. I am OK if the some messaged are getting enqueued, But what > happened here it is processing the Old messages which are already > Delivered. > For Example: > Per day There are 100,000 Message are getting processed. When I take down > the Master, Then slave is started processing message around 150,000 already > delivered message, which 1.5 days old. > > Thanks, > Ram > > > On Wed, Feb 19, 2014 at 11:18 AM, Torsten Mielke-3 [via ActiveMQ] < > ml-node+s2283324n4678166...@n4.nabble.com> wrote: > > > Hi Ram, > > > > Assuming both broker instances master and slave work on the same levelDB > > persistence store. Is it possible that you have some messages enqueued > when > > the master broker goes down? > > When the slave takes over, it would reload the messages from the > > persistence store and hence they will be available right after startup on > > the slave broker as well. > > > > Regards, > > > > Torsten Mielke > > tmielke.blogspot.com > > > > On 19 Feb 2014, at 07:29 am, ramdassv <[hidden email]< > http://user/SendEmail.jtp?type=node&node=4678166&i=0>> > > wrote: > > > > > Here is the my implementation we have in production, We have Master > > Slave > > > with LevelDB for persistence. For some reason when Master node goes > down > > or > > > getting restarted the Queue is getting initialized with some already > > > Delivered message. Is there some setting we are missing. > > > Thanks, > > > Ram > > > > > > > > > > > > -- > > > View this message in context: > > > http://activemq.2283324.n4.nabble.com/Activemq-issue-when-Slave-started-tp4678113.html > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > > > > > > > > > > > ------------------------------ > > If you reply to this email, your message will be added to the discussion > > below: > > > > > http://activemq.2283324.n4.nabble.com/Activemq-issue-when-Slave-started-tp4678113p4678166.html > > To unsubscribe from Activemq issue when Slave started, click here< > http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4678113&code=cnZlbmthZGFzd2FteUBhcHB0aXZvLm5ldHw0Njc4MTEzfDE4MDMyMzY5ODE= > > > > . > > NAML< > http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Activemq-issue-when-Slave-started-tp4678113p4678182.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
