I spent a little time this evening going through the JDBC persistence code,
and I see no code that is specific to MariaDB and no code that appears to
handle database connection failures by seamlessly failing over to a slave
node. So if your question is simply "is there a feature to allow seamless
f
Can you please give more details about your setup? Are you using one broker
and one MariaDB cluster with three nodes? Or do you have three ActiveMQ
brokers that each have a standalone MariaDB instance? Or something else?
I think you're describing a clustered MariaDB setup where the broker stays
up
Good morning,
We have ActiveMQ setup and connected to 3 databases, 1 Master and 2 slaves
and running MariaDB. If the Master goes down for any reason, the 2 slaves
will error out and go out of sync instead of one of them becoming the new
Master. To work around this during updates, we update the two
