ZhangCheng
You can check the test coverage on this page: https://app.codecov.io/gh/apache/shardingsphere
Thanks for your feedback,now only the same connection is used on the same data source in the same transaction in the XA transaction, even if multiple connections are configured by...
@strongduanmu I want to investigate the issue,please assign me.
Hi,@I-Love-China By the pr https://github.com/apache/shardingsphere/pull/21207. It guarantees that one transaction on a dataSource use the same connection, but may cause more memory consumption, because due to the limit of the...
@zhaojinchao95 I want to investigate the issue, please assign me.
> @FlyingZC I have already checked out the problem, please help to review OK.
Hi,can you try the latest version, 4.x version is no longer maintained.
You can check the test coverage on this page: https://app.codecov.io/gh/apache/shardingsphere
You can see how to configure transaction provider in these docs. - https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/yaml-config/rules/transaction/ - https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/special-api/transaction/bitronix/ - https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/special-api/transaction/narayana/
Are you interested in trying to supplement this document.