Seata 0.8.1 当执行batch修改时报Unable to commit against JDBC Connection问题

最新推荐文章于 2024-04-26 00:56:45 发布
最新推荐文章于 2024-04-26 00:56:45 发布
阅读量4.2k 收藏 2
点赞数 2
分类专栏： Seata
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/mutian6655/article/details/103359544
版权

目录

环境

  • Seata 0.8.1

问题描述

项目中使用Seata解决分布式事务问题，一开始都很正常，可在一次事务更新的条数增多后，开始出现异常，StackTrace如下：

Caused by: java.lang.RuntimeException: org.springframework.orm.jpa.JpaSystemException: Unable to commit against JDBC Connection; nested exception is org.hibernate.TransactionException: Unable to commit against JDBC Connection
org.springframework.orm.jpa.JpaSystemException: Unable to commit against JDBC Connection; nested exception is org.hibernate.TransactionException: Unable to commit against JDBC Connection
	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:351)
	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:253)
	at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:536)
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:746)
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:714)
	at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:534)
	at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:305)
	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:98)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688)
	at com.sanfenqiu.innerbuy.dal.agent.prov.impl.order.OrderRepositoryImpl$$EnhancerBySpringCGLIB$$be944e1a.saveForOpen(<generated>)
	at com.alibaba.dubbo.common.bytecode.Wrapper88.invokeMethod(Wrapper88.java)
	at com.alibaba.dubbo.rpc.proxy.javassist.JavassistProxyFactory$1.doInvoke(JavassistProxyFactory.java:47)
	at com.alibaba.dubbo.rpc.proxy.AbstractProxyInvoker.invoke(AbstractProxyInvoker.java:76)
	at com.alibaba.dubbo.config.invoker.DelegateProviderMetaDataInvoker.invoke(DelegateProviderMetaDataInvoker.java:52)
	at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:56)
	at io.seata.integration.dubbo.alibaba.TransactionPropagationFilter.invoke(TransactionPropagationFilter.java:61)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.ExceptionFilter.invoke(ExceptionFilter.java:62)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.TimeoutFilter.invoke(TimeoutFilter.java:42)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.protocol.dubbo.filter.TraceFilter.invoke(TraceFilter.java:78)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.ContextFilter.invoke(ContextFilter.java:73)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.GenericFilter.invoke(GenericFilter.java:138)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.ClassLoaderFilter.invoke(ClassLoaderFilter.java:38)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.EchoFilter.invoke(EchoFilter.java:38)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol$1.reply(DubboProtocol.java:104)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.handleRequest(HeaderExchangeHandler.java:96)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:173)
	at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:51)
	at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:57)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.hibernate.TransactionException: Unable to commit against JDBC Connection
	at org.hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.commit(AbstractLogicalConnectionImplementor.java:87)
	at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:272)
	at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:104)
	at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:532)
	... 39 more
Caused by: java.sql.SQLException: io.seata.core.exception.TransactionException: Response[TransactionException[null]]
	at io.seata.rm.datasource.ConnectionProxy.recognizeLockKeyConflictException(ConnectionProxy.java:135)
	at io.seata.rm.datasource.ConnectionProxy.processGlobalTransactionCommit(ConnectionProxy.java:184)
	at io.seata.rm.datasource.ConnectionProxy.commit(ConnectionProxy.java:161)
	at org.hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.commit(AbstractLogicalConnectionImplementor.java:81)
	... 42 more
Caused by: io.seata.core.exception.TransactionException: Response[TransactionException[null]]
	at io.seata.rm.AbstractResourceManager.branchRegister(AbstractResourceManager.java:68)
	at io.seata.rm.DefaultResourceManager.branchRegister(DefaultResourceManager.java:96)
	at io.seata.rm.datasource.ConnectionProxy.register(ConnectionProxy.java:207)
	at io.seata.rm.datasource.ConnectionProxy.processGlobalTransactionCommit(ConnectionProxy.java:182)
	... 44 more

	at com.alibaba.dubbo.rpc.filter.ExceptionFilter.invoke(ExceptionFilter.java:106)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.TimeoutFilter.invoke(TimeoutFilter.java:42)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.protocol.dubbo.filter.TraceFilter.invoke(TraceFilter.java:78)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.ContextFilter.invoke(ContextFilter.java:73)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.GenericFilter.invoke(GenericFilter.java:138)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.ClassLoaderFilter.invoke(ClassLoaderFilter.java:38)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.filter.EchoFilter.invoke(EchoFilter.java:38)
	at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol$1.reply(DubboProtocol.java:104)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.handleRequest(HeaderExchangeHandler.java:96)
	at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:173)
	at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:51)
	at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:57)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	... 1 common frames omitted

问题排查

从异常分析得知，问题出在seata身上，且必然出现更新的条数少时没有问题，多时开始报错。定位Seata源码(AbstractResourceManager.java:68)，发现是RM从TC返回错误，但一个TransactionException[null]报得不明不白。

    @Override
    public Long branchRegister(BranchType branchType, String resourceId, String clientId, String xid, String applicationData, String lockKeys) throws TransactionException {
        try {
            BranchRegisterRequest request = new BranchRegisterRequest();
            request.setXid(xid);
            request.setLockKey(lockKeys);
            request.setResourceId(resourceId);
            request.setBranchType(branchType);
            request.setApplicationData(applicationData);

            BranchRegisterResponse response = (BranchRegisterResponse) RmRpcClient.getInstance().sendMsgWithResponse(request);
            if (response.getResultCode() == ResultCode.Failed) {
>>>>            throw new TransactionException(response.getTransactionExceptionCode(), "Response[" + response.getMsg() + "]");
            }
            return response.getBranchId();
        } catch (TimeoutException toe) {
            throw new TransactionException(TransactionExceptionCode.IO, "RPC Timeout", toe);
        } catch (RuntimeException rex) {
            throw new TransactionException(TransactionExceptionCode.BranchRegisterFailed, "Runtime", rex);
        }
    }

开始尝试升级Seata，将seata-all由原来的v0.8.1升级为0.9.0.1，然而问题依然存在。
即然是从TC报的错误，就决定去TC看一下，果不其然，seata-service报错如下：

2019-12-02 19:53:10,354 ERROR Failed to add branchSession to globalSession:Data truncation: Data too long for column 'lock_key' at row 1

io.seata.common.exception.StoreException: Data truncation: Data too long for column 'lock_key' at row 1
        at io.seata.core.store.db.LogStoreDataBaseDAO.insertBranchTransactionDO(LogStoreDataBaseDAO.java:389)
        at io.seata.server.store.db.DatabaseTransactionStoreManager.writeSession(DatabaseTransactionStoreManager.java:113)
        at io.seata.server.session.db.DataBaseSessionManager.addBranchSession(DataBaseSessionManager.java:127)
        at io.seata.server.session.AbstractSessionManager.onAddBranch(AbstractSessionManager.java:131)
        at io.seata.server.session.GlobalSession.addBranch(GlobalSession.java:214)
        at io.seata.server.coordinator.DefaultCore.lambda$branchRegister$0(DefaultCore.java:82)
        at io.seata.server.session.GlobalSession.lockAndExcute(GlobalSession.java:594)
        at io.seata.server.coordinator.DefaultCore.branchRegister(DefaultCore.java:66)
        at io.seata.server.coordinator.DefaultCoordinator.doBranchRegister(DefaultCoordinator.java:186)
        at io.seata.server.AbstractTCInboundHandler$4.execute(AbstractTCInboundHandler.java:148)
        at io.seata.server.AbstractTCInboundHandler$4.execute(AbstractTCInboundHandler.java:144)
        at io.seata.core.exception.AbstractExceptionHandler.exceptionHandleTemplate(AbstractExceptionHandler.java:117)
        at io.seata.server.AbstractTCInboundHandler.handle(AbstractTCInboundHandler.java:144)
        at io.seata.core.protocol.transaction.BranchRegisterRequest.handle(BranchRegisterRequest.java:136)
        at io.seata.server.coordinator.DefaultCoordinator.onRequest(DefaultCoordinator.java:473)
        at io.seata.core.rpc.DefaultServerMessageListenerImpl.onTrxMessage(DefaultServerMessageListenerImpl.java:87)
        at io.seata.core.rpc.netty.RpcServer.dispatch(RpcServer.java:266)
        at io.seata.core.rpc.netty.AbstractRpcRemoting$3.run(AbstractRpcRemoting.java:371)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'lock_key' at row 1
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4230)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4164)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2615)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2776)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2838)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2082)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2334)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2262)
        at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2246)
        at com.alibaba.druid.pool.DruidPooledPreparedStatement.executeUpdate(DruidPooledPreparedStatement.java:256)
        at io.seata.core.store.db.LogStoreDataBaseDAO.insertBranchTransactionDO(LogStoreDataBaseDAO.java:387)
        ... 21 common frames omitted

问题解决

  • seata-service的表branch_table的lock_key定义为varchar(128)，批量修改时不能满足需求。将lock_key修改为text，问题解决。

  • 翻看官方的GitHub，发现官方也于今天(2019.12.02)在develop版上修复了这个问题 feature: solve the lock_key length problem #1905，相信不久的release，就会解决这个问题。

明谨
关注
  • 2
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 5
    评论
专栏目录
seata0.8.1
05-21
Seata 的版本 0.8.1 是其发展过程中的一个重要里程碑，带来了诸多改进和优化。下面将详细探讨 Seata 的核心功能、工作原理以及在 0.8.1 版本中的特性。 ### Seata 的核心功能 1. **全局事务（Global Transaction）...
seata 0.8.1-1.1.0（windows）.zip
04-11
由于国内下载比较慢，故上传自github上下载的分布式事务中间件Seata，版本有V0.8.1、V0.9.0、V1.0.0-GA、V1.1.0，供大家下载使用，V1.0.0-GA及V1.1.0没有sql脚本
seata 提交全局事务失败 Unable to commit against JDBC Connection
lishuzhen5678的博客
01-14 5581
前言 将s...
Caused by: org.hibernate.TransactionException: unable to commit against JDBC connection
牛栏山矿泉水
11-05 1817
1、错误描述 Caused by: org.hibernate.TransactionException: unable to commit against JDBC connection at org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doCommit(JdbcTransaction.java:116) a...
Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection；
最新发布
qq_69588103的博客
04-26 2907
Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
org.hibernate.TransactionException: unable to commit against JDBC connection
信徒博客
03-20 1万+
错误背景 ssh项目一个Action请求转发到另一个请求 <action name="replay_op" class="replayOperator" method="replay_ask"> <result name="success" type="redirect">/details.kk?post_id=${post_id}</result> ...
seata报错问题总结 Unable to commit against JDBC Connection
qq_33286156的博客
12-07 3072
Unable to commit against JDBC Connection
Communications link failure
一起进步的博客
08-05 553
经过排查发现是sql 语句执行时间过长，导致连接池断开连接。优化sql 语句， 或者延长连接超时时间。
seata 0.8.1-1.1.0（LINUX版）.zip
04-11
由于国内下载比较慢，故上传自github上下载的分布式事务中间件Seata，版本有V0.8.1、V0.9.0、V1.0.0-GA、V1.1.0，供大家下载使用，V1.0.0-GA及V1.1.0没有sql脚本
seata-0.8.1.zip
01-19
分布式事务框架(Seata)介绍 Seata:Simple Extensible Autonomous Transaction Architecture，简易可扩展的自治式分布式事务管理框架，其前身是fescar。阿里巴巴GTS的开源版实现，是一种分布式事务的解决方案，...
seata-0.8.1:seata原始码解析-源码解析
03-24
Seata：简单的可扩展的自主事务架构 什么是西塔？ 高性能且易于使用的分布式事务解决方案，可用于微服务体系结构。 微服务中的分布式事务问题 让我们想象一下传统的单片应用程序。 它的业务由3个模块组成。 他们...
org.springframework.orm.jpa.JpaSystemException问题记录
热门推荐
程序员涂小哥的技术博客
01-11 3万+
最近在使用jpa的过程中出现了如下异常： org.springframework.orm.jpa.JpaSystemException: could not execute statement; nested exception is org.hibernate.exception.GenericJDBCException: could not execute statement at
分布式事务SEATA遇到的死锁问题
qq_40594135的博客
09-07 2183
记录一次分布式事务SEATA遇到的巨坑报错，开发环境没有问题，但是测试环境频繁出现事务报错。 报错提示： org.springframework.orm.jpa.JpaSystemException: Unable to commit JDBC Connection;nested exception is org.hibernate.TransactionException:Unable to commit against JDBC Connection 在开发环境从没遇过这样的报错，但是测试环境经常会
org.springframework.orm.jpa.JpaSystemException: ids for this class must be manually assigned before
N_007的博客
05-16 1975
在使用 Spring JPA 进行数据库保存操作时，提示该错误 错误意思是 在调用save()方法之前之前，必须手动添加此类的ID。 数据库 id 字段已设置自动增长，发现实体类 id 并未设置自动增长属性，加入 @GeneratedValue(strategy = IDENTITY) 标签即可 @Id @GeneratedValue(strategy = IDENTITY) private Long id; ...
org.springframework.orm.jpa.JpaSystemException
Angus
09-22 3760
错误回放： org.springframework.orm.jpa.JpaSystemException: Null value was assigned to a property of primitive type setter of com.rails.air.dataserver.entity.KTOrderMainEntity.flag1; nested exception i...
数据库连接异常
YourGhost_的博客
12-16 764
先说一下项目背景，这个问题困扰了我很久。 背景：公司一个和京东合作的项目，初期公司比较有钱，花大钱投入，后面公司效益不好，投的钱少了，用户也就少了，大概项目上线后一年多，经常有用户投诉说页面无法访问，并且公司监控系统也监控到服务器响应时间超长，查了后台日志，unable to commit against JDBC connection或者which is more than the configured time (StuckThreadMaxTime) of “600” seconds. Stack t
org.springframework.orm.jpa.JpaSystemException&&org.hibernate.InstantiationException
Dreamlike_的博客
12-02 681
Exception in thread “main” org.springframework.orm.jpa.JpaSystemException: No default constructor for entity: : com.qf.bean.Teacher; nested exception is org.hibernate.InstantiationException: No defa...
org.springframework.orm.jpa.JpaSystemException: could not execute query;
weixin_43114485的博客
07-10 8422
报错来源: 在配置好的idea上,把代码生成器自动生成的代码导入带项目中,直接进行findALl全查,报错,如下图: 尝试解决方法: 数据库运行sql语句,查询成功,数据ok, 数据乱码: 数据库编码格式utf8,数据库可插入正常中文 清空缓存,重新编译,重启idea, JpaSystemException 重新生成 反复n遍 … 最终解决方法: 数据库字段有字段type:datet...
java事物 commit失败_seata 提交全局事务失败 Unable to commit against JDBC Connection
06-08
这个错误可能是由于以下原因导致的： 1. 分布式事务管理器Seata未正确配置或启动。 2. 数据库连接池中的连接已关闭或丢失。 3. 事务中发生了异常，导致无法提交事务。 解决这个问题的方法包括： 1. 检查Seata的配置和启动状态，确保它与应用程序协同工作。 2. 确保数据库连接池中的连接可用，并且可以正确地访问数据库。 3. 检查应用程序中的代码，查看是否有任何异常抛出，导致事务无法提交。 如果以上方法无法解决问题，建议您查看日志文件，以获取更详细的错误信息，并进行必要的调试和排查。

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值