hua74ni opened a new issue, #23517: URL: https://github.com/apache/shardingsphere/issues/23517
## Bug Report ### Which version of ShardingSphere did you use? 5.3.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? Hybrid Architecture, ShardingSphere-JDBC ### Expected behavior one ShardingSphere-JDBC startup and register **1** JDBC worker ### Actual behavior one ShardingSphere-JDBC startup and register **10** JDBC worker ### Reason analyze (If you can) There are doubts about the shardingSphere-JDBC startup initialization data source logic: datasource(tomcat) -> datasourcePool（tomcat，loop 10 times，Cause subsequent initialization and register for 10 times） -> Trigger shardingsphere driver (there is a cache in the middle logic that does not seem to meet the expected cache) -> register shardingSphere-JDBC worker(10 workers) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. Hybrid Architecture of registry zookeeper, The configuration is on ShardingSphere-Proxy, ShardingSphere-JDBC is configured in spring boot mode. document: https://shardingsphere.apache.org/document/5.3.0/cn/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/spring-boot/ ### Example codes for reproduce this issue (such as a github link). the ShardingSphere-JDBC configuration: **pom.xml**  **Configure Spring Boot Properties** ``` spring.datasource.driver-class-name=org.apache.shardingsphere.driver.ShardingSphereDriver spring.datasource.url=jdbc:shardingsphere:classpath:shardingsphere.yaml ``` **shardingsphere.yaml** ``` mode: type: Cluster repository: type: ZooKeeper props: namespace: governance server-lists: localhost:2181 databaseName: database_name ``` framework: Springboot 1.5.22 + Jpa -- 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]
