I opened https://issues.apache.org/activemq/browse/AMQ-2463 to track this. There should be no bad consequences, it is just a performance issue as read_uncommitted is a dirty state that we can live with. But more strict isolation like repeatable_read, which is needed for bin-log will work also.
2009/1/18 old_dog <[email protected]> > > I use mysql master-master replication,so I have to open bin-log. When > activemq starts it throws an Exception : > > ERROR DefaultDatabaseLocker - Failed to acquire lock: > java.sql.SQLException: 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' > > If I turn useDatabaseLock off, the activemq can start. But later, it throws > exception: > > WARN JDBCPersistenceAdapter - Old message cleanup failed due to: > java.sql.SQLException: Binary logging not possible. Message: Transaction > level 'READ-UNCOMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT' > INFO TransportServerThreadSupport - Listening for connections at: > tcp://0.0.0.0:61616 > INFO TransportConnector - Connector openwire Started > INFO BrokerService - ActiveMQ JMS Message Broker > (localhost, ID:infoscape-52221-1232257218444-0:0) started > > > then it dies soon. > > I wonder why the transaction level 'READ-UNCOMMITED' is set? I changed the > source, and recompiled. Then activemq seem to run well. But is there any > bad influence? > > -- > View this message in context: > http://www.nabble.com/ActiveMQ-can-not-start-when-mysql-bin-log-is-opened-tp21527285p21527285.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
