activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Blich <...@tomblich.com>
Subject ActiveMQ fails to create tables in MySql 5.1.40sp1
Date Tue, 17 Aug 2010 05:25:58 GMT

I get error messages when it first creates the tables, when then I get a
message that it can't create the lock. 

I'm trying to use a mysql database as a shared storage mechanism.   

Java Runtime: Sun Microsystems Inc. 1.6.0
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre
  Heap sizes: current=8896k  free=7185k  max=466048k
    JVM args: -Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true
-Djava.util.logging.config.file=logging.properties
-Dcom.sun.management.jmxremote
-Dactivemq.classpath=/u0/apache-activemq/conf;
-Dactivemq.home=/u0/apache-activemq -Dactivemq.base=/u0/apache-activemq
ACTIVEMQ_HOME: /u0/apache-activemq
ACTIVEMQ_BASE: /u0/apache-activemq
Loading message broker from: xbean:activemq.xml
 INFO | Using Persistence Adapter:
JDBCPersistenceAdapter(org.apache.commons.dbcp.BasicDataSource@2911ded2)
 INFO | Database adapter driver override recognized for :
[mysql-ab_jdbc_driver] - adapter: class
org.apache.activemq.store.jdbc.adapter.MySqlJDBCAdapter
 WARN | Could not create JDBC tables; they could already exist. Failure was:
CREATE INDEX ACTIVEMQ_MSGS_MIDX ON ACTIVEMQ_MSGS (MSGID_PROD,MSGID_SEQ)
Message: Binary logging not possible. Message: Transaction level
'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
SQLState: HY000 Vendor code: 1598
 WARN | Failure details: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

java.sql.SQLException: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
 WARN | Could not create JDBC tables; they could already exist. Failure was:
CREATE INDEX ACTIVEMQ_MSGS_CIDX ON ACTIVEMQ_MSGS (CONTAINER) Message: Binary
logging not possible. Message: Transaction level 'READ-UNCOMMITTED' in
InnoDB is not safe for binlog mode 'STATEMENT' SQLState: HY000 Vendor code:
1598
 WARN | Failure details: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
java.sql.SQLException: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

 WARN | Could not create JDBC tables; they could already exist. Failure was:
CREATE INDEX ACTIVEMQ_MSGS_EIDX ON ACTIVEMQ_MSGS (EXPIRATION) Message:
Binary logging not possible. Message: Transaction level 'READ-UNCOMMITTED'
in InnoDB is not safe for binlog mode 'STATEMENT' SQLState: HY000 Vendor
code: 1598
 WARN | Failure details: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
java.sql.SQLException: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

 WARN | Could not create JDBC tables; they could already exist. Failure was:
INSERT INTO ACTIVEMQ_LOCK(ID) VALUES (1) Message: Binary logging not
possible. Message: Transaction level 'READ-UNCOMMITTED' in InnoDB is not
safe for binlog mode 'STATEMENT' SQLState: HY000 Vendor code: 1598
 WARN | Failure details: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
java.sql.SQLException: Binary logging not possible. Message: Transaction
level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

 INFO | Database lock driver override not found for :
[mysql-ab_jdbc_driver].  Will use default implementation.
 INFO | Attempting to acquire the exclusive lock to become the Master broker
 INFO | Failed to acquire lock.  Sleeping for 1000 milli(s) before trying
again...
 INFO | Failed to acquire lock.  Sleeping for 1000 milli(s) before trying
again...
 INFO | Failed to acquire lock.  Sleeping for 1000 milli(s) before trying
again...
 INFO | Failed to acquire lock.  Sleeping for 1000 milli(s) before trying
again...
 INFO | Failed to acquire lock.  Sleeping for 1000 milli(s) before trying
again...

-- 
View this message in context: http://old.nabble.com/ActiveMQ-fails-to-create-tables-in-MySql-5.1.40sp1-tp29449218p29449218.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message