apache/incubator-seata

用户不分服务，操作同库，导致XA、AT模式下使用的异常情况

Open

#5,502 创建于 2023年4月10日

在 GitHub 查看
 (3 评论) (0 反应) (1 负责人)Java (25,960 star) (8,878 fork)batch import
good first issuetask: help-wanted

描述

  • I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

如果用户不分服务，操作同库，jdbcurl相同，导致通过resourceId获取数据源错误，获取不到链接，二阶段下发commit/rollback报错xaer_nota错误；#5034，虽然这个pr在一阶段hold了所有链接，如果在oracle同库不同用户下，在一阶段完成后，二阶段服务重启，导致holder没值，可能会造成ORA-24774问题

所以我认为resourceId可能得唯一，才能根本上解决问题

由于我对AT模式代码不太熟悉，这里就暂且不讨论了。

Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

Just paste your stack trace here!

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. xxx
  2. xxx
  3. xxx

Minimal yet complete reproducer code (or URL to code):

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

  • JDK version(e.g. java -version):
  • Seata client/server version:
  • Database version:
  • OS(e.g. uname -a):
  • Others:

贡献者指南

技术栈
javasql
领域
backenddatabase
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
5
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of distributed transaction conceptsFamiliarity with Seata XA/AT modesJava development experienceKnowledge of database connection pooling
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
Investigate the resource ID uniqueness problem in Seata's XA/AT mode. Review issue #5502 and related PR #5034. Examine how Seata manages data sources via resourceId in the TransactionManager and ResourceManager components. Consider proposing a solution to ensure resourceId uniqueness across services sharing the same JDBC URL, such as appending a service identifier. Check the Seata source code in modules such as rm datasource and core for relevant classes.