JMS之——ActiveMQ启动时报锁定数据库的问题解决

最新推荐文章于 2019-07-03 21:37:08 发布
最新推荐文章于 2019-07-03 21:37:08 发布
阅读量3k 收藏 3
点赞数 4
分类专栏： 精通消息中间件系列 文章标签： JMS ActiveMQ
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/l1028386804/article/details/69027456
版权

转载请注明出处：http://blog.csdn.net/l1028386804/article/details/69027456

原因是：activeMQ的broker在启动时会锁定数据库。我们每个人在调试时，自己的运行环境中就会运行一个broker，所以会出现争用锁的现象（如果只有一个人运行则不会出现这样的问题），报错如下：

2017-04-03 16:21:13,481 | WARN  | Could not create JDBC tables; they could already exist. Failure was: INSERT INTO ACTIVEMQ_LOCK(ID) VALUES (1) Message: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. SQLState: HY000 Vendor code: 1665 | org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter | main
2017-04-03 16:21:13,490 | WARN  | Failure details: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED. | org.apache.activemq.store.jdbc.JDBCPersistenceAdapter | main
java.sql.SQLException: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1084)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4232)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4164)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2615)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2776)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2832)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2781)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:908)[mysql-connector-java-5.1.30-bin.jar:]
	at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:788)[mysql-connector-java-5.1.30-bin.jar:]
	at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)[commons-dbcp-1.4.jar:1.4]
	at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)[commons-dbcp-1.4.jar:1.4]
	at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)[commons-dbcp-1.4.jar:1.4]
	at org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.executeStatement(DefaultJDBCAdapter.java:114)[activemq-jdbc-store-5.14.4.jar:5.14.4]
	at org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.doCreateTables(DefaultJDBCAdapter.java:92)[activemq-jdbc-store-5.14.4.jar:5.14.4]
	at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.init(JDBCPersistenceAdapter.java:304)[activemq-jdbc-store-5.14.4.jar:5.14.4]
	at org.apache.activemq.broker.LockableServiceSupport.preStart(LockableServiceSupport.java:89)[activemq-broker-5.14.4.jar:5.14.4]
	at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:54)[activemq-client-5.14.4.jar:5.14.4]
	at org.apache.activemq.broker.BrokerService.doStartPersistenceAdapter(BrokerService.java:675)[activemq-broker-5.14.4.jar:5.14.4]
	at org.apache.activemq.broker.BrokerService.startPersistenceAdapter(BrokerService.java:659)[activemq-broker-5.14.4.jar:5.14.4]
	at org.apache.activemq.broker.BrokerService.start(BrokerService.java:623)[activemq-broker-5.14.4.jar:5.14.4]
	at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:73)[activemq-spring-5.14.4.jar:5.14.4]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_45]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_45]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
	at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1700)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1639)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1568)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755)[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:762)[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480)[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE]
	at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:64)[xbean-spring-4.2.jar:4.2]
	at org.apache.xbean.spring.context.ResourceXmlApplicationContext.<init>(ResourceXmlApplicationContext.java:52)[xbean-spring-4.2.jar:4.2]
	at org.apache.activemq.xbean.XBeanBrokerFactory$1.<init>(XBeanBrokerFactory.java:104)[activemq-spring-5.14.4.jar:5.14.4]
	at org.apache.activemq.xbean.XBeanBrokerFactory.createApplicationContext(XBeanBrokerFactory.java:104)[activemq-spring-5.14.4.jar:5.14.4]
	at org.apache.activemq.xbean.XBeanBrokerFactory.createBroker(XBeanBrokerFactory.java:67)[activemq-spring-5.14.4.jar:5.14.4]
	at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:71)[activemq-broker-5.14.4.jar:5.14.4]
	at org.apache.activemq.broker.BrokerFactory.createBroker(BrokerFactory.java:54)[activemq-broker-5.14.4.jar:5.14.4]
	at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:87)[activemq-console-5.14.4.jar:5.14.4]
	at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)[activemq-console-5.14.4.jar:5.14.4]
	at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:154)[activemq-console-5.14.4.jar:5.14.4]
	at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:63)[activemq-console-5.14.4.jar:5.14.4]
	at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:104)[activemq-console-5.14.4.jar:5.14.4]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_45]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_45]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_45]
	at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_45]
	at org.apache.activemq.console.Main.runTaskClass(Main.java:262)[activemq.jar:5.14.4]
	at org.apache.activemq.console.Main.main(Main.java:115)[activemq.jar:5.14.4]
2017-04-03 16:21:13,526 | INFO  | Database lock driver override not found for : [mysql_connector_java].  Will use default implementation. | org.apache.activemq.store.jdbc.JDBCPersistenceAdapter | main
2017-04-03 16:21:13,535 | INFO  | Attempting to acquire the exclusive lock to become the Master broker | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:21:13,617 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:21:23,623 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:21:33,629 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:21:43,635 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:21:53,640 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:22:03,643 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:22:13,648 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:22:23,651 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:22:33,656 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:22:43,662 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:22:53,670 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:23:03,675 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:23:13,685 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:23:23,693 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
2017-04-03 16:23:33,699 | INFO  | Failed to acquire lock.  Sleeping for 10000 milli(s) before trying again... | org.apache.activemq.store.jdbc.DefaultDatabaseLocker | main
处理办法：在config的activemq.xml中，修改jdbcPersistenceAdapter选项，添加一个：useDatabaseLock="false"，结果如下： 
<jdbcPersistenceAdapter dataDirectory="activemq-data" useDatabaseLock="false" transactionIsolation="4" dataSource="#mysql-ds"/>

冰 河
关注
  • 4
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 1
    评论
专栏目录
ActiveMQ中使用mysql做持久化报错：Cannot execute statement: impossible to write to binary log since BINLOG_FORM
KimmKing的技术博客
01-02 2万+
ActiveMQ中如果使用mysql innodb的同时，开启了binlog，那么在ack消息的时候，日志里就可会报错：java.sql.SQLException: Cannot execute statement: binlogging impossible since BINLOG_FORMAT = STATEMENT and at least one table uses a storage
服务器activemq启动不了问题排查
生如夏花之灿烂
03-15 9155
在重启activemq的过程中遇到一些问题，记录如下： 进入到activemq的bin目录，执行./activemq start命令， 然后查看端口61616是否占用：netstat -tlnp|grep 61616, 发现并没有启动，进入activemq安装目录/data/目录下查看日志：tail -1000f activemq.log,发现链接数据库被拒绝， 于是进入conf/目录下查...
ActiveMQ学习（二）
qq_37113604的博客
07-03 321
消息的发送策略 持久化消息，默认情况下，生产者发送的消息时持久化的。消息发送到broker后，producer会等待broker对这条消息的处理情况的反馈，默认情况是同步的需要堵塞等待，效率较低，可以设置消息发送端发送持久化消息的异步方式。 connectionFactory.setUseAsyncSend(true) 回执窗口大小设置，通过这个来控制borker在确认收到消息前，生产者...
ActiveMQ启动时报锁定数据库的问题解决
坐忘峰
06-27 7839
原因是：activeMQ的broker在启动时会锁定数据库。我们每个人在调试时，自己的运行环境中就会运行一个broker，所以会出现争用锁的现象（如果只有一个人运行则不会出现这样的问题），报错如下： 2012-06-27 15:12:32 org.apache.activemq.store.jdbc.JDBCPersistenceAdapter INFO D atabase lock driv
Activemq 启动分析
DaemonSu
11-10 1714
Activemq 启动分析   Active的启动是从org.apache.activemq.console中的Main类中启动的。   启动中的命令模式   我这里传递参数如下：   -Xms1G -Xmx1G -Djava.util.logging.config.file=logging.properties -Dhawtio.realm=activemq -Dhawt
activemq leveldb切换jdbc主从模式
噜噜噜的博客
08-03 690
之前一直在用levedb持久化模式，LevelDB存储已被弃用，官方不再支持或建议使用,并且从 ActiveMQ 4.1 版本开始支持 JDBC 主从集群。 在mq进程启动时一个主（某一台mq进程）抓取数据库中表的独占锁，另一台mq进程会由于争抢不到表锁而阻塞，这样其它的进程都变成了从。（只允许有一个主，可以有多个从）  如果主的服务断开或者服务中断（比如进程中断、机器宕机等），它（原来的主）...
深入掌握JMS——ActiveMQ 十一章
12-26
深入掌握JMS——ActiveMQ 十一章pdf,收集整理
JMS.rar_activemq_jms_jms activemq
09-24
利用ActiveMQ中间件发送JMS消息的例子
ActiveMQ——Java连接ActiveMQ
02-24
topic不保存消息它是无状态的不落地，假如无人订阅就去生产，那就是一条废消息，所以，一般先启动消费者再启动生产者JMS规范允许客户创建持久订阅，这在一定程度上放松了时间上的相关性要求。持久订阅允许消费者消费...
JMS简介与ActiveMQ实战代码分享
08-28
主要介绍了JMS简介与ActiveMQ实战代码分享，具有一定借鉴价值,需要的朋友可以参考下
JMS之ActiveMQ视频教程+源码
09-01
一头扎进JMS之ActiveMQ，主要讲解ActiveMq的使用，内带视频源码，基础讲解。接口分析。
ActiveMQ中使用mysql做持久化报错：Cannot execute statement: impossible to write to binary l
IT382566697的专栏
08-18 263
  ActiveMQ中如果使用mysql innodb的同时，开启了binlog，那么在ack消息的时候，日志里就可会报错：java.sql.SQLException: Cannot execute statement: binlogging impossible since BINLOG_FORMAT = STATEMENT and at least one table uses a s...
Cannot execute statement in a READ ONLY transaction.
weixin_41010294的博客
03-25 8849
报错如下： Cause: java.sql.SQLException: Cannot execute statement in a READ ONLY transaction. ; uncategorized SQLException for SQL []; SQL state [25006]; error code [1792]; Cannot execute statement in a R...
JMS学习笔记6
日蚀
08-02 2507
JMS服务器ActiveMQ的初体验并持久化消息到MySQL数据库中. 1、下载AMQ：http://activemq.apache.org/download.html，最新版本是5.5.0； 2、解压apache-activemq-5.5.0-bin
InnoDB Read-Only Transactions_只读事务
weixin_34364135的博客
11-10 212
2019独角兽企业重金招聘Python工程师标准>>> ...
Mycat使用遇到的错误
热门推荐
另一个世界
07-18 3万+
仅用于记录个人使用中碰到的错误1.错误 com.mysql.jdbc.PacketTooBigException: Packet for query is too large (44 > -1). You can change this value on the server by setting the max_allowed_packet’ variable。 原因 将版本更换为5.1.3
关于MYCAT 读写分离,与只读事务的问题.
weixin_30552811的博客
09-18 868
习惯性为了复用mysql连接,喜欢加上@Transactional(readOnly = true) 只读事务,很多零碎的查询下,速度会快一些,也环保一些. 最近用mycat做了读写分离,其中一个查询加上了@Transactional(readOnly = true) ,居然出来了错误的数据, 删除事务后,数据正确,想了半天,是否读库写库的数据可能不一致.经过比较,果然有一条数据不一致 加上...
Activemq-5.15.5启动报错 ERROR | Failed to start Apache ActiveMQ (localhost, ID:N666_LDD-50099-1553217453
LTY_Sun的博客
03-22 2588
错误信息如下： STATUS | wrapper | 2019/03/22 09:17:32 | --> Wrapper Started as Console STATUS | wrapper | 2019/03/22 09:17:32 | Launching a JVM... INFO | jvm 1 | 2019/03/22 09:17:32 | Wrapper (...
Cause: java.sql.SQLException: Cannot execute statement: impossible to write to binary log
csdnhadoop的博客
04-19 3328
额外遇到的问题 Cause: java.sql.SQLException: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based lo
activemq topic cpu高_Java学习之——ActiveMQ
最新发布
05-23
如果你在使用 ActiveMQ 的时候发现 CPU 占用率过高，那么可能是以下原因导致的： 1. 消息消费者数量过多，导致消息处理的压力过大，从而导致 CPU 占用率升高。 2. 消息生产者发送速度过快，导致消息堆积，从而导致...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

冰 河

可以吃鸡腿么？

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值