1.5.2版本 TCC模式注册分支问题 #7574
1.5.2版本 TCC模式注册分支问题
#7574
-
|
我有两个应用 A 和 B，A使用AT模式 ，B使用TCC模式，并且A作为消费者 通过Dubbo消费 B，我发现在分布式事务过程中，A应用除了会注册一次AT模式的分支外， 还会注册一次TCC模式的分支；导致在事务提交阶段，这两个分支都会被提交，然后B的 commit不仅会被seata调用一次，还会被A的通过dubbo调用一次，请问这种情况是不可避免的吗？ |
Beta Was this translation helpful? Give feedback.
Answered by
funky-eyes
Aug 6, 2025
Replies: 1 comment
-
|
Upgrade to version 2.0 or above, or avoid placing TCC annotations on interfaces. Instead, place them in the provider's implementation class. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
funky-eyes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrade to version 2.0 or above, or avoid placing TCC annotations on interfaces. Instead, place them in the provider's implementation class.