Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of tmielke@redhat.com designates
 209.132.183.28 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Activemq issue when Slave started
From: Torsten Mielke <tmielke@redhat.com>
In-Reply-To: <1392791372947-4678113.post@n4.nabble.com>
Date: Wed, 19 Feb 2014 20:17:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8741158E-7727-41BB-B6D6-2C71658CE56E@redhat.com>
References: <1392791372947-4678113.post@n4.nabble.com>
To: users <users@activemq.apache.org>

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.=20

Regards,

Torsten Mielke
tmielke.blogspot.com

On 19 Feb 2014, at 07:29 am, ramdassv <rvenkadaswamy@apptivo.net> 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. =20
> Thanks,
> Ram
>=20
>=20
>=20
> --
> View this message in context: =
http://activemq.2283324.n4.nabble.com/Activemq-issue-when-Slave-started-tp=
4678113.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.