> I was trying to do similar things with data replication provider, but found
> the remaining messages were not processed by the newly elected HA singleton
> provider, and seemed to be lost. I am not sure if this is doable.

You'll have to go into more detail here for me to help further.  A full 
description of the use-case, configuration, expected outcome, and actual 
outcome would be a good place to start.

For the most part the semantics of shared-store and replication are the same, 
but there are places where this is not true because (surprise!) the 
implementations are different.  I'm not sure you've run into one of those 
places because I'm not totally clear on what exactly you're doing.

I mentioned this on the Wildfly forum thread [1] you opened about this issue, 
but I suppose it bears repeating.  You're mixing the Wildfly application 
server's implementation of HA singleton with Artemis' implementation of HA, and 
Artemis doesn't have a notion of HA singleton.  You might be better of 
splitting Artemis from the application server so each can be configured as 
necessary.


Justin

[1] https://developer.jboss.org/thread/271845

----- Original Message -----
From: "wwang2016" <wayne.w...@impactmobile.com>
To: users@activemq.apache.org
Sent: Friday, August 12, 2016 7:45:29 AM
Subject: Re: How to configure colocated backup servers for data replication 
approach

Hi Justin,

I was able to test the scenario with collocated shared-store approach with
two wildfly instances which are set up as HA singleton (only one wildfly
will be active at anytime). The following is the configuration

wildfly #1 (master1 activemq + slave1 activemq)
wildfly #2 (master2 activemq + slave2 activemq)

The directories for master1 activemq are referenced by slave2 activemq and
the directories for master2 activemq are referenced by slave1 activemq.

When I start up these two wildfly instances in order, the one that was
started up earlier will be HA singleton provider, and the other will be
standby. I was able to test HA for messaging by shutting down the current HA
singleton provider while it is in the process of processing messages (the
remaining messages will be processed by the newly elected HA singleton
provider).

I was trying to do similar things with data replication provider, but found
the remaining messages were not processed by the newly elected HA singleton
provider, and seemed to be lost. I am not sure if this is doable.

Thanks,

Wayne



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/How-to-configure-colocated-backup-servers-for-data-replication-approach-tp4715415p4715445.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to