Hi,
The colocated backup servers for shared store approach is to set up a backup
server which basically read the messages that are written by another
instance of live server.
instance #1(master.1 + slave.1)
instance #2 (master.2 + slave.2)
Where the directory of slave.1 is the same as that of m
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
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
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
Hi,
I set up two wildfly instances (activemq is imbeded) in a cluster using
shared-store approach. I was testing the messaging high availability by
allow one wildfly instance (#1) to create all messages, and both instances
were able to process the messages. In the middle, I shut down instance #1,
I tried to set the permission of the folder so that the user who started the
application has full control, and the issue persisted.
One more observation:
(1) let instance #1 create all 1 messages, the paging folder was created
with a paging file
(2) both instance #1 and instance#2 were process
