首页 / MYSQL / 在JBoss 5.1中的MDB(ActiveMQ)中捕获MySQL死锁

在JBoss 5.1中的MDB(ActiveMQ)中捕获MySQL死锁

内容导读

互联网集市收集整理的这篇技术教程文章主要介绍了在JBoss 5.1中的MDB(ActiveMQ)中捕获MySQL死锁，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含15428字，纯文字阅读大概需要23分钟。

内容图文

我们使用JBoss 5.1 w / MDB支持ActiveMQ RAR.

当消耗队列上的消息并执行某些数据库操作然后导致死锁时,死锁基本上是在重新启动JBoss的整个实例之前.通过软管,该队列上消耗的所有后续消息都会失败,并出现以下异常：

Caused by: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection

死锁异常从不引用我的代码,这反过来使我很难捕获和处理.

例如,以下是死锁异常的例外：

2012-06-18 18:52:19,848 WARN   [JDBCExceptionReporter] : SQL Error: 1213, SQLState: 40001
2012-06-18 18:52:19,848 ERROR  [JDBCExceptionReporter] : Deadlock found when trying to get lock; try restarting transaction
2012-06-18 18:52:19,850 ERROR  [AbstractFlushingEventListener] : Could not synchronize database state with session
org.hibernate.exception.LockAcquisitionException: Could not execute JDBC batch update
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:105)
        at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
        at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:275)
        at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:266)
        at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168)
        at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321)
        at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
        at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
        at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:365)
        at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:504)
        at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:101)
        at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:269)
        at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:89)
        at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1423)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.endTransaction(MessageInflowLocalProxy.java:435)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.finish(MessageInflowLocalProxy.java:314)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.after(MessageInflowLocalProxy.java:230)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:136)
        at $Proxy677.afterDelivery(Unknown Source)
        at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:128)
        at org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:69)
        at org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:224)
        at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:897)
        at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
        at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
        at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.BatchUpdateException: Deadlock found when trying to get lock; try restarting transaction
        at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2013)
        at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1449)
        at com.mysql.jdbc.jdbc2.optional.StatementWrapper.executeBatch(StatementWrapper.java:721)
        at org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:774)
        at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70)
        at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268)
        ... 29 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)
        at com.mysql.jdbc.Util.getInstance(Util.java:382)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1064)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3603)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3535)
         at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1989)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2150)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2626)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415)
        at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1976)
        ... 34 more
2012-06-18 18:52:19,851 WARN   [arjLoggerI18N] : [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] TwoPhaseCoordinator.beforeCompletion - failed for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@480671ab
javax.persistence.PersistenceException: org.hibernate.exception.LockAcquisitionException: Could not execute JDBC batch update
        at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614)
        at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:513)
        at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:101)
        at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:269)
        at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:89)
        at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1423)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.endTransaction(MessageInflowLocalProxy.java:435)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.finish(MessageInflowLocalProxy.java:314)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.after(MessageInflowLocalProxy.java:230)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:136)
        at $Proxy677.afterDelivery(Unknown Source)
        at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:128)
        at org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:69)
        at org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:224)
        at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:897)
        at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
        at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
        at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.hibernate.exception.LockAcquisitionException: Could not execute JDBC batch update
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:105)
        at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
        at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:275)
        at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:266)
        at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168)
        at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321)
        at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50)
        at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
        at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:365)
        at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:504)
        ... 22 more
Caused by: java.sql.BatchUpdateException: Deadlock found when trying to get lock; try restarting transaction
        at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2013)
        at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1449)
        at com.mysql.jdbc.jdbc2.optional.StatementWrapper.executeBatch(StatementWrapper.java:721)
        at org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:774)
        at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70)
        at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268)
        ... 29 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
                at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)
        at com.mysql.jdbc.Util.getInstance(Util.java:382)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1064)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3603)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3535)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1989)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2150)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2626)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415)
        at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1976)
        ... 34 more
2012-06-18 18:52:19,912 WARN   [TxConnectionManager] : Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@6acc2da9[state=NORMAL mc=org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@2c9e906 handles=0 lastUse=1340059939649 permit=true trackByTx=true mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@10015060 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@4643d6d5 xaResource=org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@2c9e906 txSync=null]
com.mysql.jdbc.jdbc2.optional.MysqlXAException: XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected
        at com.mysql.jdbc.jdbc2.optional.MysqlXAConnection.mapXAExceptionFromSQLException(MysqlXAConnection.java:605)
        at com.mysql.jdbc.jdbc2.optional.MysqlXAConnection.dispatchCommand(MysqlXAConnection.java:584)
        at com.mysql.jdbc.jdbc2.optional.MysqlXAConnection.end(MysqlXAConnection.java:479)
        at org.jboss.resource.adapter.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:246)
        at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:396)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3270)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:3248)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1933)
        at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:97)
        at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1423)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.endTransaction(MessageInflowLocalProxy.java:435)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.finish(MessageInflowLocalProxy.java:314)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.after(MessageInflowLocalProxy.java:230)
        at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:136)
        at $Proxy677.afterDelivery(Unknown Source)
        at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:128)
        at org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:69)
        at org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:224)
        at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:897)
        at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
        at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
        at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
2012-06-18 18:52:19,914 INFO   [ServerSessionImpl:153] : Endpoint failed to process message. Reason: Endpoint after delivery notification failure

我可以捕获后续错误(后续消息到队列的错误)：

引起：javax.persistence.PersistenceException：org.hibernate.exception.GenericJDBCException：无法打开连接

但我甚至不知道该如何处理它,也许我可以得到一个新的EntityManager,但不是我已经通过注入开始……我知道解决这个错误的唯一方法就是重新开始.

我假设最初的死锁是作为结束队列中的事务的一部分发生的,这就是为什么它不会发生在我的代码中,但是我知道一种方法可以优雅地处理这个问题吗？

更新：

>所有DataSource都是MySQL XA
>在transaction-jboss-beans.xml中,我们将transactionTimeout设置为300

解决方法:

无法正常处理容器事务异常.

它决定回滚无论原因是什么,你无法控制它.获得有关此类异常和回滚事件的通知的复杂选项可能是编写JCA连接器,该连接器将虚假资源注册到每个MDB事务的分布式事务管理器中.

我建议你调查一下发生了什么,并从源头解决问题.

这是一个死锁场景,它总是涉及多个线程：如果两个代码使用相同的实体但顺序不同,则第一个线程将锁定资源A(行,表或Java监视器)并等待B当第二个线程已经锁定资源B并且现在等待A.

因此,Java监视器和数据库资源之间可能存在分布式死锁,这种情况很难诊断.整个系统一直停留,直到两端的事务超时,必须扫描Java线程转储和数据库会话和锁.

在您的情况下,由于MySQL检测到死锁本身,这意味着只涉及数据库资源.

为了提供帮助,我想你应该减少一次JMS消息(一次事务)的批量更新中运行的SQL查询的数量.在同时消耗并发消息的情况下,处理应用大量行的事务时,更可能发生死锁情况.

但奇怪的是,由于仅使用DB死锁,您的JBoss服务器在回滚后会卡住：

>要么已经耗尽了DataSource池中的JDBC连接数
>或者没有更多的MySQL服务器端连接可用
>或者所有消息bean也处于死锁状态
>事务超时可能太高,无法在合理的时间范围内获得回滚

因此,要么通过缩小相应池的大小来减少MDB并发性,要么减少每个事务的更新次数 – 甚至可能只有每个JMS消息一次更新…

内容总结

以上是互联网集市为您收集整理的在JBoss 5.1中的MDB(ActiveMQ)中捕获MySQL死锁全部内容，希望文章能够帮你解决在JBoss 5.1中的MDB(ActiveMQ)中捕获MySQL死锁所遇到的程序开发问题。如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。

内容备注

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容，请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。

内容手机端

扫描二维码推送至手机访问。

本文链接：https://qyyshop.com/info/903023.html

来源：【匿名】

【上一篇】mysql – Joomla jos_session表崩溃【下一篇】用IE远程创建Mysql数据库的简易程序

更多 ►

【在JBoss 5.1中的MDB(ActiveMQ)中捕获MySQL死锁】教程文章相关的互联网学习教程文章

Nignx负载均衡存在的seesion问题mysql集群负载均衡负载均衡器activemq负载均【图】

*当使用权或者轮训访问服务器的时候，两次访问产生的session不在同一台服务器，造成了session找不到解决方案：1.可以暂时用ip_hash策略来绑定用户到某一个服务器上2.通过session复制,服务器网络广播（网络复核压力比较大，只要一个session里面的一个键改变都会进行session同步）（1）在tomcat.xml里面设置开启session复制的选项（2）在我们应用程序中设置支持分布式web.xml中设置,在文件加入,在tomcat配置文件中设置 (3) 额外创建一...

JMS服务器ActiveMQ的初体验并持久化消息到MySQL数据库中【图】

<persistenceAdapter> <jdbcPersistenceAdapter dataSource="#MySQL-DS"/></persistenceAdapter>该配置表示，我们将要使用一个叫做“MySQL-DS”的JDBC数据源；3、配置MySQL数据源：在</broker>节点后面，增加MySQL数据源配置： <bean id="MySQL-DS" class="org.apache.commons.dbcp.BasicDat...

Apache ActiveMQ 持久化到MySQL数据库

前言ActiveMQ 是Apache出品，最流行的，能力强劲的开源消息总线。ActiveMQ 是一个完全支持JMS1.1和J2EE 1.4规范的 JMSProvider实现，尽管JMS规范出台已经是很久的事情了，但是JMS在当今的J2EE应用中间仍然扮演着特殊的地位。关于ActiveMQ 的详细介绍请参考：http://baike.baidu.com/view/433374.htm?fr=aladdin关于JMS的详细介绍请参考：http://baike.baidu.com/subview/157103/12665866.htm?fr=aladdinActiveMQ提供多种数据持久化...

java高级软件架构师实战视频教程 Spring+Mybatis+SpringMVC+Ehcache+Memcached+Redis+Nginx+Varnish+ActiveMQ+Keepalived+MySQL+MongoDB

迅雷下载　　百度云第001节：整体课程概览第002节：分模块、分工程管理第003节：多模块多Web应用合并War包第004节：Git基本原理和安装配置使用第005节：TortoiseGit的本地使用第006节：Egit的本地使用第007节：远程使用以及冲突解决第008节：基本业务功能和数据字典第009节：搭建基础的开发环境第010节：Spring+Mybatis实现DAO第011节：Mybatis的分页实现第012节：Service的实现以及模块化第013节：Spring MVC实现Web层开发第014...

activemq持久化配置，设置为主从模式（带复制的主从模式，应用mysql数据库）

配置文件如下<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the"License"); you may not use this file except in compliance with the License. You may ...

activemq持久化之mysql配置【图】

参考：http://blog.csdn.net/zbw18297786698/article/details/52999940 说明：192.168.3.81 CentOS release 6.5 apache-activemq-5.10.1 1、拷贝mysql驱动器到activemq环境下 mysql-connector-java-5.1.44-bin.jar [root@node-01 apache-activemq-5.10.1]# ls /home/apache-activemq-5.10.1/lib/mysql-connector-java-5.1.44-bin.jar 2、创建保存activemq消息的数据库 mysql> CREATE DATABASE test_mq DEFAULT CHARACTER SET u...

记录activemq 配置mysql 持久化入得坑【代码】

="org.apache.commons.dbcp.BasicDataSource2" destroy-method="close"><property name="driverClassName" value="com.mysql.jdbc.Driver"/><property name="url" value="jdbc:mysql://localhost/activemq"/><property name="username" value="root"/><property name="password" value="root"/><property name="maxActive" value="200"/><property name="poolPreparedStatements" value="true"/></bean>被这个坑的很惨然后关于avt...

activeMQ发布订阅模式中中常用工具类

package com.jms;import java.util.Map;import java.util.concurrent.ConcurrentHashMap;import javax.jms.BytesMessage;import javax.jms.Connection;import javax.jms.ConnectionFactory;import javax.jms.Destination;import javax.jms.JMSException;impopackage com.jms;import java.util.Map; import java.util.concurrent.ConcurrentHashMap;import javax.jms.BytesMessage; import javax.jms.Connection; import javax.jms....

1ActiveMQ使用2ActiveMQC#Client实现3ActiveMQC++Client实现通【图】

Active MQ使用 http://www.huaishao8.com/tag/activemq Kagula 2011-9-6 介绍 Active MQ是个消息队列管理器，用于通讯的中间件。 Java Active MQ的常见使用方式有两种：[1]点对点方式(Producer/Consumer)[2]发布/订阅者方式（Publisher/Subscriber Model）Active MQ使用 http://www.huaishao8.com/tag/activemqKagula 2011-9-6 介绍Active MQ是个消息队列管理器，用于通讯的中间件。 Java + Active MQ的常见使用方式有两种：[1]点对...

JMS消息持久化，将ActiveMQ消息持久化到mySql数据库中_MySQL

ActiveMQ5.8.0版本采用kahadb作为默认的消息持久化方式。使用默认的持久化机制，我们不容易直接看到消息究竟是如何持久的。ActiveMQ提供的JDBC持久化机制，能够将持久化信息存储到数据库。通过查看数据库中ActiveMQ生成的表结构和存储的数据，能够帮助我们更好的了解消息的持久化机制。现在介绍如何配置activemq，将数据持久化到mysql中。1.配置activeMQ需要的mySql数据源为了能够使用JDBC访问mysql数据库，显然必须要配置消息服务...

ActiveMq——mysql8.0以上版本连接配置【代码】【图】

步骤： 1、修改配置文件 1.1 找到ActiveMq安装目录，打开conf文件夹， 1.2 打开activeMq.xml 1.3 在beans中添加mysql的bean <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close"> <property name="driverClassName" value="com.mysql.cj.jdbc.Driver"/> <property name="url" value="jdbc:mysql://localhost:3306/activemq?characterEncoding=utf8&...

Spring整合ActiveMQ持久化到Mysql数据库【图】

一、ActiveMQ为什么需要持久化消息持久化就是将消息保存到磁盘上,这样的好处就是即使Activemq服务挂了,消息还保存在磁盘不会丢失,服务重新启动之后还能找到消息并再次发送,消息的持久化和消息的发送模型是没有关系的. 二、队列的持久化(队列默认是持久化的)1、Spring的配置文件(配置文件路径和名称 resources/conf/spring/applicationContext.xml)<context:co...

Activemq5.15.5持久化到mysql8.0.20【图】

一、环境Activemq:5.15.5Mysql:8.0.20这里面一定要针对自己的环境进行配置,以前用的是mysql 5.x的版本,然后切换为8.0x的版本,各种报错,有配置文件的错误,有mysql授权远程登录等等... 二、引入jar包到Activemq安装目录下我这里Activemq的安装目录是(/usr/local/activemq/apache-activemq-5.15.5),为了避免出错这个mysql数据库的驱动包请保持和你自己windows上安装的版本一模一样. 三、替换Activemq默认的持久化方式具体的配置如下...