-
Notifications
You must be signed in to change notification settings - Fork 203
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
SnappyData-1.3.0 JDBC connection is not working. #1569
Comments
Are you able to resolve the connection issue? I am also facing the same while trying to connect cluster from local snappy cli.
|
Connecting to JDBC from client gives below error:
java.sql.SQLException: (SQLState=40XD0 Severity=30000) ([hostname[1527]]) Container has been closed or has moved from 'hostname[1528]' {failed after trying all available servers: {hostname[1528]=hostname[1528], 10.49.3.107[1528]=10.49.3.107[1528], hostname[1527]=DEV-BDSP-Worker-07[1527]}, secondary-locators=[hostname[1528]]}.
Where as connection works if we run the program locally.
Below is the code snippet.
`try
{
private static final String JDBC_URL = "jdbc:snappydata://%1$s:%2$s/";
1.Tried with both 1527 and 1528 ports.
2.Please find the below locator log
21/12/30 04:44:36.961 PST main<tid=0x1> INFO LocatorImpl: Starting Thrift locator on: DEV-BDSP-Worker-07/10.49.3.107[1527]
21/12/30 04:44:37.038 PST main<tid=0x1> INFO LocatorImpl: Started Thrift locator (Compact Protocol) on: DEV-BDSP-Worker-07/10.49.3.107[1528]
It is trying to start Locator on port 1527 as well as 1528
3.Connection used to work with snappydata-1.1.0.
4.Connection on same machine works if we switch to SnappyData 1.1.0.
5.OS info as below
NAME="Red Hat Enterprise Linux Server"
VERSION="7.7 (Maipo)"
6.Another observation in new snappydata is clicking on members on 5050 UI gives below error:
HTTP ERROR 400
Problem accessing /dashboard/memberDetails/. Reason:
7.No error are seen on startup.
Please let us know the solution.
The text was updated successfully, but these errors were encountered: