lcn事务不生效
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
1、已经按照文档排除了，并且进入DataSourceAspect。
2、调用方，和被调用方，我全部用的注解@LcnTransaction
3、调用方式feign。
调用两个服务以后更新数据以后，下一步有一个异常使流程报错，但是数据库依然更新，并没有进行回滚，版本5.0.2.RELEASE,以下是代码片段。
// feign调用
Object mobile = userService.updateMobile("18292822257");
// feign调用
Object token = userService.updateToken("apple two");
log.warn("token: {},mobile :{}",token,mobile);
int bug = 1 / 0;
/**
* 被调用方
* @param token
* @return
*/
@Override
@Transactional
@LcnTransaction
public R updateToken(String token) {
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Feign call flow shown in the issue, including updateMobile, updateToken, and the later division-by-zero exception. Start by tracing DataSourceAspect and the @LcnTransaction/@Transactional entry points; done means both service updates are rolled back when the caller fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100