Is there a reason you don’t look at replicates journal setup? Journal is the primary and most performant way to run, especially in a scalable way which is what multi master is about.
JDBC really is just for retro users, you won’t get benefit from multi master as you will have the shared single JDBC backend as your bottle neck Sent from my iPhone > On 24 Apr 2018, at 11:12, Francesco Nigro <nigro....@gmail.com> wrote: > > Hi Archibald! > > If you want to have 3 servers running over the same shared store I think > you have to choose 1 to be the live and the remaining 2 to be backups. > > If you want to have 3 live servers, each one with shared store HA you need > to specify for each [live, backups] group a different node manager store > table > (for the journal too) to allow live and backup locks to be handled > correctly.. > > Cheers, > Franz > > > Il giorno mar 24 apr 2018 alle ore 10:29 Archibald <arch...@gmx.net> ha > scritto: > >> Hi, >> >> I'm trying to create an environment with 3 live servers and a shared >> JDBC-Store. >> But this obviously failes due to live locks (all are using the same >> NODE_MANAGER_STORE table). >> >> So first server starts fine. >> Second doesn't (timeout waiting for live lock). >> Third doesn't (timeout waiting for live lock). >> >> Is there a way to run this scenario successfully? >> >> Thanks, >> Archibald. >> >> >> >> -- >> Sent from: >> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >>
