Ⅰ. Issue Description
全局事务入口方法在 tcc接口实现类导致全局事务开启失败
Ⅱ. Describe what happened
Just paste your stack trace here!
把事务入口单独抽一个bean就可以正常开启事务
Ⅵ. Environment:
- JDK version(e.g.
java -version): 8 - Seata client/server version: 1.5.2
- Database version: 5.7.1
- OS(e.g.
uname -a): windows - Others:
3条答案
按热度按时间k4ymrczo1#
seata 1.5.2 can't meet the situation, only generate tcc proxy. 2.0 have resolved the problem.
j91ykkif2#
这个问题社区已经发现，是因为proxyparser发现其中一个注解时就返回，没有考虑有多层注解，需要多层代理的情况
The problem community has discovered that proxyparser returns one of the annotations when it finds it, regardless of the multiple layers of annotations. Cases where a multi-tier agent is required
js5cn81o3#
谢谢tks