报错: com.atomikos.datasource.ResourceException: resume for XID

简介: 报错: com.atomikos.datasource.ResourceException: resume for XID

出现这种情况,按照步骤尝试下:

 

1. 先不动配置, 检查是否存在事务重叠开启的情况,就是接口开了事务,里面方法还开了事务,而且事务有冲突。

 

2.在你的数据连接url后面加上   &pinGlobalTxToPhysicalConnection=true


        url: jdbc:mysql://localhost:3306/mydb?useUnicode=true&characterEncoding=utf-8&useSSL=false&serverTimezone=GMT%2B8&pinGlobalTxToPhysicalConnection=true&autoReconnect=true


3.酌情试着把这个设置为 true


image.png


如果按照上面三个步骤都做了设置,还是频繁出现这个错误的话,那加油。

相关文章
|
缓存 NoSQL Java
【异常】com.alicp.jetcache.CacheException: refresh error
【异常】com.alicp.jetcache.CacheException: refresh error
177 1
|
11月前
|
Java 关系型数据库 MySQL
定时任务Quzrtz:Failed to override connection auto commit/transaction isolation
定时任务Quzrtz:Failed to override connection auto commit/transaction isolation
111 0
[已解决]SpringDataJPA+Hibernate在执行executeUpdate()的时候报错 Executing an update/delete query
[已解决]SpringDataJPA+Hibernate在执行executeUpdate()的时候报错 Executing an update/delete query
|
关系型数据库 MySQL
ERROR com.alibaba.druid.pool.DruidDataSource - create connection SQLException, url
ERROR com.alibaba.druid.pool.DruidDataSource - create connection SQLException, url
3076 0
ERROR com.alibaba.druid.pool.DruidDataSource - create connection SQLException, url
|
缓存 Oracle 关系型数据库
Oracle中控制commit的三个参数 commit_write, commit_logging和 commit_wait
Oracle中控制commit的动作有三个参数 commit_write, commit_logging和 commit_wait,按重要性分别说明如下
271 0
|
关系型数据库 MySQL Java
Could not open Hibernate Session for transaction; nested exception is org.hibernate.TransactionExcep linux下mysql修改连接超时wait_timeout修改后就ok了
Could not open Hibernate Session for transaction; nested exception is org.hibernate.TransactionExcep linux下mysql修改连接超时wait_timeout修改后就ok了
179 1
|
druid
报错: com.alibaba.druid.pool.DruidDataSource : abandon connection, owner thread
报错: com.alibaba.druid.pool.DruidDataSource : abandon connection, owner thread
1099 0
报错: com.alibaba.druid.pool.DruidDataSource : abandon connection, owner thread
|
Java Apache
journalnode Can't scan a pre-transactional edit log异常处理
一个测试环境hadoop集群由于磁盘满导致宕机,启动后发现journalnode报如下异常: 2018-03-19 20:48:04,817 WARN  namenode.
2745 0