Skip to content
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

Shardingsphere-proxy + seate update database exception Cause: java.sql.SQLException: Internal error: io.seata.core.exception.RmTransactionException: branch register failed #28721

Closed
asdf112255 opened this issue Oct 11, 2023 · 4 comments

Comments

@asdf112255
Copy link

Question

i use shading-proxy +seate with springboot app,
query data is right,
when i update database (insert/update/delete) i got exception below:

Error updating database. Cause: java.sql.SQLException: Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454713603026944, errMsg: TransactionException[branch register request failed. xid=172.28.201.95:30095:455454713603026944, msg=Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454714349613056, errMsg: TransactionException[Could not found global transaction xid = 172.28.201.95:30095:455454714349613056, may be has finished.] ] ### The error may exist in jnpf/engine/mapper/FlowTaskMapper.java (best guess) ### The error may involve defaultParameterMap ### The error occurred while setting parameters ### SQL: DELETE FROM flow_task WHERE (F_ID IN (?)) ### Cause: java.sql.SQLException: Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454713603026944, errMsg: TransactionException[branch register request failed. xid=172.28.201.95:30095:455454713603026944, msg=Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454714349613056, errMsg: TransactionException[Could not found global transaction xid = 172.28.201.95:30095:455454714349613056, may be has finished.] ] ; uncategorized SQLException; SQL state [HY000]; error code [1815]; Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454713603026944, errMsg: TransactionException[branch register request failed. xid=172.28.201.95:30095:455454713603026944, msg=Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454714349613056, errMsg: TransactionException[Could not found global transaction xid = 172.28.201.95:30095:455454714349613056, may be has finished.] ] ; nested exception is java.sql.SQLException: Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454713603026944, errMsg: TransactionException[branch register request failed. xid=172.28.201.95:30095:455454713603026944, msg=Internal error: io.seata.core.exception.RmTransactionException: branch register failed, xid: 172.28.201.95:30095:455454714349613056, errMsg: TransactionException[Could not found global transaction xid = 172.28.201.95:30095:455454714349613056, may be has finished.] ]

do i need any another configuration?
shardingsphere server.conf:
transaction:
defaultType: BASE
providerType: Seata
seata.conf:
client {
application.id = risk
transaction.service.group = my_test_tx_group
}
any suggestion is appreciate!:)

Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

@github-actions github-actions bot added the stale label Nov 10, 2023
@linghengqian
Copy link
Member

i use shading-proxy +seate with springboot app,

  • Are you using io.seata.spring.annotation.GlobalTransactional? I suspect this has been declared in Bump io.seata:seata-all for testing to 2.0.0 #30146 . If you are using io.seata:seata-spring-boot-starter, please turn off its automatic proxy data source function through the Spring Boot configuration file.

Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

@github-actions github-actions bot added the stale label Mar 19, 2024
@linghengqian
Copy link
Member

  • Closing this issue because it cannot be reproduced.

@linghengqian linghengqian self-assigned this Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants