We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在使用TCC模式下时,调用到commit方法和rollback方法时,方法内BusinessActionContext.getBranchType()得到内容为null。
If there is an exception, please attach the exception trace:
Minimal yet complete reproducer code (or URL to code):
目前调试发现在org.apache.seata.rm.tcc.TCCResourceManager中branchCommit方法和branchRollback方法参数中有branchType值且取值正常,但方法体中未使用该值(包括创建BusinessActionContext对象)。 当前代码仓库中也未使用该值TCCResourceManager
java -version
uname -a
The text was updated successfully, but these errors were encountered:
I suspect this is a bug. Could you submit a PR to fix this issue?
Sorry, something went wrong.
@Yang-xingchen If you’re busy and don’t have time, I’d be happy to take on this issue :)
@YongGoose ok,I am still learning Seata and not very familiar with it yet. You can fix it.
Thanks!
I’ll reach out if I need any help while working on the issue. 🙂
No branches or pull requests
Ⅰ. Issue Description
在使用TCC模式下时,调用到commit方法和rollback方法时,方法内BusinessActionContext.getBranchType()得到内容为null。
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Minimal yet complete reproducer code (or URL to code):
Ⅴ. Anything else we need to know?
目前调试发现在org.apache.seata.rm.tcc.TCCResourceManager中branchCommit方法和branchRollback方法参数中有branchType值且取值正常,但方法体中未使用该值(包括创建BusinessActionContext对象)。
当前代码仓库中也未使用该值TCCResourceManager
Ⅵ. Environment:
java -version
): 21uname -a
): Linux zk1 5.18.15-1.el7.elrepo.x86_64 fescar init #1 SMP PREEMPT_DYNAMIC Thu Jul 28 09:26:15 EDT 2022 x86_64 x86_64 x86_64 GNU/LinuxThe text was updated successfully, but these errors were encountered: