justbk2015 opened a new issue #12672: URL: https://github.com/apache/shardingsphere/issues/12672
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - 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? master ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? proxy ### Expected behavior when scaling task over and I restart proxy, I can use gsql connect to opengauss. ### Actual behavior I can use gsql connect to opengauss, the return info is: gsql: received invalid response to SSL negotiation: j. ### Reason analyze (If you can) 1. the reason is FrontDatabaseProtocolTypeFactory::getDatabaseType function use invalid schema to set databaseType to default. (default is MySQL),. 2.because when scaling task running, it add logic_db on governance_ds/metadata/, but this schema dataSources is empty. getDatabaseType only use first schema (this is logic) , and that databaseType is MySQL， so error occur. 3. I guess use postgrsql database have some problem. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1. open sharding-proxy zookeeper config and scaling config, then start 2. start sharding-scaling 3. create a scaling job (no need wait this job over, just when zookeeper have logic_db node in governance_ds/metadata/) 4. delete job from zookeeker 5. restart sharding-proxy 6. use gsql connect to openguass, judje if can connect success. ### Example codes for reproduce this issue (such as a github link). no need. -- 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]
