It also probably wouldn't be that hard for you to implement a Zookeeper-based Locker if that sounded more appealing than a SQL database, since it sounds like you might feel negatively about using an RDBMS.
If you do, we'd love have you donate it back to the community if your company would allow it; that lets other people benefit from what you implemented and (key point) means that we - not you - are on the hook for long-term maintenance. Tim On Oct 31, 2017 4:11 PM, "Johan Edstrom" <seij...@gmail.com> wrote: > Using JDBC you can get both. > > > > <persistenceAdapter> > <kahaDB directory="target/activemq-data" lockKeepAlivePeriod="5000"> > <locker> > <!-- When used with the KahaDB persistence adapter the > 'dataSource' attribute must be defined on the locker itself: --> > <lease-database-locker lockAcquireSleepInterval="10000" > dataSource="#mysql-ds"> > <statements> > <!-- Default locker attributes and SQL statements may > be overridden here > using one or more <statements > attribute_or_statement="value"/> entries: --> > <statements lockTableName="activemq_lock"/> > </statements> > </lease-database-locker> > </locker> > </kahaDB> > </persistenceAdapter> > > > > > > On Oct 31, 2017, at 4:06 PM, akhil <akh...@gmail.com> wrote: > > > > Hello Everyone , > > > > I just had an issue today with the Active MQ EFS where one of the master > > lost its mount and two brokers acted as a master master instead of > complete > > failover. I have just looked at the pluggable storage lockers but it was > all > > giving that locks to JDBC stores not the EFS ones . Is there any > recommended > > way of using the correct setting or pluggable lockers for the EFS boxes > to > > make a correct failover ? I am using amq version 5.13.4. > > > > Please suggest options. > > > > Thanks, > > Akhil. > > > > > > > > -- > > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html > >