-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
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
浏览器请求调用方服务超时后,数据死锁问题 #556
Comments
@1991wangliang 作者大大帮忙看看,用在生产了,项目在上线了,比较急:0 |
好像暂时没有更好的方案了,只能把超时时间改长一点 # 分布式事务执行总时间(ms). 默认为36000
tx-lcn.manager.dtx-time=60000 |
@longxiaonan 哥们 你好 请问你的问题解决了吗 我们生产也出现和你一样的问题,求解 |
不好意思,没关注到消息,后面我们用的seata了 |
您好,您的来信我已收到!谢谢!
Best Wishes!
——孔祥亮
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
问题描述:
依照下面的代码进行描述,我在调用方服务中设置Thread.sleep(10000)来模拟浏览器调用超时的情况。浏览器请求
controller
,访问调用方服务的startFlow
方法,第一次请求log如下:浏览器再次请求,log如下:
debug查看到是卡在
mapper.updateById(order);
这里,在mysql执行SELECT * FROM INFORMATION_SCHEMA.INNODB_TRX;
可以看到这个的update语句出现了lock wait。等大概20秒左右,lock wait消失,页面请求失败。后面页面每次请求都是这个死锁的情况。调用方代码:
被调用方代码:
The text was updated successfully, but these errors were encountered: