Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect to ShardingSphere-Proxy #34179

Open
flyer5200 opened this issue Dec 27, 2024 · 2 comments
Open

Unable to connect to ShardingSphere-Proxy #34179

flyer5200 opened this issue Dec 27, 2024 · 2 comments

Comments

@flyer5200
Copy link

Bug Report

I use shardingsphere-proxy version 5.5.1, and the client cannot connect to the proxy, and the following error appears:

Unknown exception. More details: java.lang.NullPointerException: Cannot invoke “org.apache.shardingsphere.infra.metadata.database.ShardingSphereDatabase.getRuleMetaData()” because the return value of “org.apache.shardingsphere.infra.metadata.ShardingSphereMetaData.getDatabase(String)” is null

Version: ShardingSphere-Proxy 5.5.1 cluster mode (zookeeper)

image
image

@terrymanu
Copy link
Member

How to reproduce it?

@flyer5200
Copy link
Author

Please refer to the steps to reproduce the #34178

This problem only exists in Alibaba Cloud DMS when performing datasource validation.
There is no such problem when using MySQL client or Navicat.

Under the premise of ensuring network connectivity, DMS will perform an instance availability check when entering the data source, usually sending select 1 to shardingsphere-proxy. At this time, the shardingsphere-proxy will throw the above exception:
Unknown exception. More details: java.lang.NullPointerException: Cannot invoke “org.apache.shardingsphere.infra.metadata.database.ShardingSphereDatabase.getRuleMetaData()” because the return value of “org.apache.shardingsphere.infra.metadata.ShardingSphereMetaData.getDatabase(String)” is null

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants