Python-IBM opened a new issue, #6236: URL: https://github.com/apache/incubator-seata/issues/6236
<!-- Please do not use this issue template to report security vulnerabilities but refer to our [security policy](https://github.com/seata/seata/security/policy). --> - [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description Implement MySQL read-write separation using shardingsphere-jdbc application configuration. When starting the application server, the registration of RM resources in seata is from the slave database, which causes the main database to be unable to roll back normally.  ### Ⅱ. Describe what happened If there is an exception, please attach the exception trace: ``` Just paste your stack trace here! ``` ### Ⅲ. Describe what you expected to happen I expect to see the RM registration main database resource of seata when the application service starts. ### Ⅳ. How to reproduce it (as minimally and precisely as possible) 1. xxx 2. xxx 3. xxx Minimal yet complete reproducer code (or URL to code): ### Ⅴ. Anything else we need to know? ### Ⅵ. Environment: - JDK version(e.g. `java -version`): 17 - Seata client/server version: 2.0 - Database version: MySQL 8.0.27 - OS(e.g. `uname -a`): Windows - Others: shardingsphere-jdbc version: 5.4.0 spring boot version: 3.2.1 -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
