dongoewang commented on issue #30242: URL: https://github.com/apache/shardingsphere/issues/30242#issuecomment-1960867733
> This means that if you are using ShardingSphere JDBC, project A may not be notified when project B throws an exception, but I am not sure if two projects use the same transaction group of Seata , whether the Seata Server side will initiate notifications to other Seata Clients in the transaction group. 1:two projects use the same transaction group of Seata; 2:it seems like the Seata Server side don't initiate notifications to other Seata Clients in the transaction group > If the Seata AT mode is integrated with a ShardingSphere Proxy instance, and project A and project B initiate transaction requests to this ShardingSphere Proxy instance through local transactions in Java or Python, it seems that this problem should not exist. 1:through debug, i knows the Seata AT mode is integrated with a ShardingSphere Proxy instance. 2:i don't know whether or not project A and project B initiate transaction requests to this ShardingSphere Proxy instance through local transactions in Java or Python @linghengqian -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
