apache / apache/incubator-seata

全局事务入口方法在 tcc接口实现类导致全局事务开启失败

Open
#6,276 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
26k
Forks
8.8k
Avg merge
1d 8h
Merged PRs (30d)
4

Description

### Ⅰ. Issue Description
全局事务入口方法在 tcc接口实现类导致全局事务开启失败

### Ⅱ. Describe what happened

```
Just paste your stack trace here!
```
![image](https://github.com/apache/incubator-seata/assets/46508112/edc2cf2b-f408-4d9f-b867-91d40e9d8520)
![image](https://github.com/apache/incubator-seata/assets/46508112/24ff2123-86c1-467b-af7c-77df5974a7c8)
把事务入口单独抽一个bean就可以正常开启事务
![image](https://github.com/apache/incubator-seata/assets/46508112/fec798ab-9b99-42c9-ac10-a5dae76811f6)

### Ⅵ. 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:

Contributor guide

Open the contributing guide

Research direction

No source files, tests, or entry points are named. Start by reproducing the failure with Seata 1.5.2, JDK 8, and the reported TCC interface arrangement, then trace global transaction startup when the entry method remains in the TCC implementation. Done means the transaction starts successfully without extracting the entry method into a separate bean.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.