I swithed to the amqPersistenceAdapter: Kaha with journal... semms to be ok!
Thanks! Gary Tully wrote: > > see http://activemq.apache.org/jdbc-support.html for some detail on > overriding the default statement set. It should be possible to > override the lock statement that is used by default. > > 2008/9/5 Fuzzo <[EMAIL PROTECTED]>: >> >> Hi all! >> >> When i try to start ActiveMQ with an HSQLDB data source i give this >> error: >> >> INFO | jvm 1 | 2008/09/05 16:55:46 | INFO BrokerService >> - Using Persistence Adapter: >> JDBCPersistenceAdaptor([EMAIL PROTECTED]) >> INFO | jvm 1 | 2008/09/05 16:55:46 | INFO JDBCPersistenceAdapter >> - Database driver recognized: [hsql_database_engine_driver] >> INFO | jvm 1 | 2008/09/05 16:55:46 | INFO DefaultDatabaseLocker >> - Attempting to acquire the exclusive lock to become the Master broker >> INFO | jvm 1 | 2008/09/05 16:55:46 | ERROR DefaultDatabaseLocker >> - Failed to acquire lock: java.sql.SQLException: Termine inaspettato: FOR >> in >> statement [SELECT * FROM ACTIVEMQ_LOCK FOR UPDATE] >> INFO | jvm 1 | 2008/09/05 16:55:46 | java.sql.SQLException: Termine >> inaspettato: FOR in statement [SELECT * FROM ACTIVEMQ_LOCK FOR UPDATE] >> >> In other words, the keyword FOR is unknown. >> All is ok with useDatabaseLock="false" set in persistenceAdapter. >> >> If the db is not locked, i can't do a Master/Slave HA cluster, isn't >> true? >> >> Thanks for all! >> -- >> View this message in context: >> http://www.nabble.com/JDBC-Master-Slave-with-HSQLDB-lock-problem%21-tp19333147p19333147.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/JDBC-Master-Slave-with-HSQLDB-lock-problem%21-tp19333147p19408761.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
