The journal is not shared, so - no it is not a good idea for master/slave http://activemq.apache.org/masterslave.html
On Oct 27, 2010, at 1:44 PM, kseelam wrote: > > Also as per the 5.4.0 schema, there is a useDatabaseLock attribute in > journalPersistenceAdapterFactory > > http://activemq.apache.org/schema/core/activemq-core-5.4.0-schema.html#journalPersistenceAdapterFactory > > Element: journalPersistenceAdapterFactory > > useDatabaseLock xs:boolean Sets whether or not an exclusive > database lock > should be used to enable JDBC Master/Slave. Enabled by default. > > This allows us to use it Journal + Jdbc master/slave. > > Any downsides of using this? > > Thank you. > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/JDBC-Master-Slave-approach-with-Journal-for-HA-tp3014521p3016176.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. Johan Edstrom j...@opennms.org They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety. Benjamin Franklin, Historical Review of Pennsylvania, 1759
