-
-
Notifications
You must be signed in to change notification settings - Fork 911
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
Illegal state: maybe the try phase operation has timed out.! try: identifier= 67fc448f057a7859a230d5236933f035, resourceKey= null, resourceXid= null. #123
Comments
2020-07-31 17:33:35.489 INFO [http-nio-9007-exec-4] o.b.bytetcc.CompensableCoordinator - 67fc6188f07a7859a230d52f42fc1fd0| compensable transaction begin! |
2020-07-31 17:33:39.421 INFO [http-nio-9006-exec-5] o.b.b.CompensableTransactionImpl - 67fc6188f07a7859a230d52f42fc1fd0| enlist remote resource: 127.0.0.1:OPEN-API-CART:9005. |
Try阶段操作先进入commit,之后超时,随后Confirm/Cancel的也进入了commit,然而如果此时Try操作的本地事务才真正完成commit操作,这时候就会出现这个提示。因为事务管理器发现当前commit的应该是Confirm/Cancel阶段本地事务,但实际上却是Try阶段的事务,与预期的不符。此时,就会抛出一个异常来终止后续全局事务状态变更。 如果业务数据并没有出现不一致,该异常可以忽略。 |
一直报这个错,导致服务调用超时了,主控服务后续的流程就无法继续进行了。请问这个问题怎么处理呀 |
try阶段操作超时情况下会报这个错,而不是报这个错导致超时。你需要做的是定位一下try阶段超时的操作。 |
遇到了一样的问题,有没有参数可以设置这个超时的时间; |
try: identifier= 67fc448f057a7859a230d5236933f035, resourceKey= null, resourceXid= null.
The text was updated successfully, but these errors were encountered: