The following is the use case:
The application is currently running as one standalone server (no cluster)
in production. We do not currently have a need to make it to run wildfly in
cluster mode, but we do have concern over a sudden shutdown of the wildfly
instance and no backup. In addition, we n
s.org/thread/271845
- Original Message -
From: "wwang2016"
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-
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 activem
hole point of fail-over.
Justin
- Original Message -
From: "wwang2016"
To: users@activemq.apache.org
Sent: Thursday, August 11, 2016 1:07:08 PM
Subject: Re: How to configure colocated backup servers for data replication
approach
Hi Justin,
I was not clear of the benefits of sett
Hi Justin,
I was not clear of the benefits of setting up a colocated backup servers
with data replication approach.
If I set up master activemq server and slave activemq server in the same
wildfly instance, then the messages will be copied from master to slave?
That does not seem to be a useful f
> What is the deal of setting up colocated backup servers for data replication
> approach?
I'm not clear on what you're asking here. Can you clarify your question?
> What are the use cases which we need to set up collocated backup? How to set
> it up?
Colocated backups are useful when you w
