开发者社区 > 云原生 > 正文

你好,请问seata1.4.2单机版本,运行几天会偶尔报找不到事务id问题,这个是bug吗?

你好,请问seata1.4.2单机版本,运行几天会偶尔报找不到事务id问题,这个是bug吗?

Error updating database. Cause: java.sql.SQLException: io.seata.core.exception.RmTransactionException: Response[ TransactionException[Could not found global transaction xid = 192.168.8.66:8091:1567649878256705825, may be has finished.] ] ### The error may exist in URL [jar:file:/E:/jar/20230526/java/market/web-1.0.1.init.jar!/BOOT-INF/lib/service-1.0.1.init.jar!/mapping/ChargeLevelMapper.xml] ### The error may involve com.dondown.mapper.ChargeLevelMapper.updateByPrimaryKeySelective-Inline ### The error occurred while setting parameters ### SQL: update charge_level SET marketName = ?, chargeId = ?, chargeName = ?, chargeType = ?, name = ?, formulaId = ?, formulaName = ?, price = ?, unit = ?, remark = ?, createTime = ? where id = ? ### Cause: java.sql.SQLException: io.seata.core.exception.RmTransactionException: Response[ TransactionException[Could not found global transaction xid = 192.168.8.66:8091:1567649878256705825, may be has finished.] ] ; uncategorized SQLException; SQL state [null]; error code [0]; io.seata.core.exception.RmTransactionException: Response[ TransactionException[Could not found global transaction xid = 192.168.8.66:8091:1567649878256705825, may be has finished.] ]; nested exception is java.sql.SQLException: io.seata.core.exception.RmTransactionException: Response[ TransactionException[Could not found global transaction xid = 192.168.8.66:8091:1567649878256705825, may be has finished.] ]

展开
收起
真的很搞笑 2023-06-06 15:53:24 163 0
1 条回答
写回答
取消 提交回答
  • 通过日志发现,没点击一次操作按钮(调用对应接口),seata控制台打印的begin全局事务id和@GlobalTransaction生成的id不一致(长时间运行几天后),所以seata服务控制台找不到对应事务,此回答整理自钉群“3群-Seata 开源讨论群”

    2023-06-06 15:59:24
    赞同 展开评论 打赏
问答分类:
问答地址:

阿里云拥有国内全面的云原生产品技术以及大规模的云原生应用实践,通过全面容器化、核心技术互联网化、应用 Serverless 化三大范式,助力制造业企业高效上云,实现系统稳定、应用敏捷智能。拥抱云原生,让创新无处不在。

相关电子书

更多
《Seata 1.3 新特性以及如何参与社区》 立即下载
低代码开发师(初级)实战教程 立即下载
阿里巴巴DevOps 最佳实践手册 立即下载