I'm not exactly sure the purpose of that entry, I guess guarantee that locking is working consistently across DBs.
If you don't want to create a row and lock on it, but rather use just the table you can set useLockCreateWhereClause to false. HTH, On 10 March 2015 at 17:41, juanmanuel.romeraferrio < juanmanuel.romerafer...@gmail.com> wrote: > Hi, I'm with a doubt about how configure fine my system. > I'm tryng to start a master/slave broker and using > createTablesOnStartup="true" in jdbcPersistenceAdapter I watched that this > create 3 tables > > ACTIVEMQ_ACKS; > ACTIVEMQ_LOCK; > ACTIVEMQ_MSGS; > > But too this create a register with ID 1 in the table ACTIVEMQ_LOCK. > My question is, I need to create this register in this table if I use > createTablesOnStartup="false"? This is the only register that i need to > create? > > Thanks > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Configure-a-Master-Slave-with-JDBC-tp4692920.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Bilgin Ibryam Red Hat, Inc. Apache Camel & Apache OFBiz committer Blog: ofbizian.com Twitter: @bibryam <https://twitter.com/bibryam> Author of Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475
