lite-up opened a new issue, #15420: URL: https://github.com/apache/shardingsphere/issues/15420
## Bug Report ### Which version of ShardingSphere did you use? shardingsphere-jdbc-core-spring-boot-starter 5.0.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior I'm currently using `DruidDataSource`, everything works fine. ### Actual behavior However, if these below conditions being met: 1. `sharding-jdbc.max-connections-size-per-query > druid.maxActive`, 2. `Actual SQLs number > druid.maxActive` and then the application will be hanging forever for waiting for the next idle `Connection`; ### Reason analyze (If you can) 1. `sharding-jdbc.max-connections-size-per-query > druid.maxActive`, 2. `Actual SQLs number > druid.maxActive` ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1. set `sharding-jdbc.max-connections-size-per-query > druid.maxActive`; 2. and then simply do some `xxxMapper.selectList(null)` to make a ALL-SHARDING-TABLES-Scanning. ### 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]
