xue2lang opened a new issue #14187: URL: https://github.com/apache/shardingsphere/issues/14187
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: **sharding-proxy when execute connection.setReadOnly(true) ,all datasource in proxy will execute "set session transaction read only"** when one connection （for datasource a）execute connection.setReadOnly(true)，other datasource b c d will change to read only，why this occur？？ - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 5.0.0-beat ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior only one datasource change to read only ### Actual behavior all datasource change to read only ### Reason analyze (If you can)  this ShardingDatabaseBroadcastRoutingEngine route all datasources ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. ### Example codes for reproduce this issue (such as a github link). -- 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]
