-
Notifications
You must be signed in to change notification settings - Fork 543
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
jdbc url set socket_timeout parameters is useless #1822
Comments
Good day, @Jiangnewtown!
Would you please describe what error do you get? I would like to understand what timeout actually happens. Thanks! |
@Jiangnewtown did it help? |
I will try it tomorrow,Thanks a lot. @chernser |
@Jiangnewtown
also you may try |
when I set the session_timeout to a lower value,the session timeout also not changed,I guess it may a bug from clickhouse server or clickhouse does not support this feature, |
@Jiangnewtown that is strange that parameter is not working - I will look into it. It should be a client side parameter only. What is your desired result? Do you want to reduce life of a connection or do you want to make it longer? I just trying to find a solution for your problem now. Thanks! |
@chernser I want to make the connection longer, I tried a lot of ways but did not find a solution. Thanks very much ! |
@Jiangnewtown |
I want to use DBeaver to connect to ClickHouse using the JDBC HTTP interface. However, the session timeout is 30 seconds. I tried adding socket_timeout=300000 to the URL settings, but it was ineffective.
I also attempted to modify the JDBC driver settings to forcibly pass the socket_timeout=300000 parameter in the HTTP URI, but an error occurred, indicating that the server does not support this parameter. Additionally, I tried changing the socket_timeout value directly in the driver settings, but it had no effect.
My question is, is there a way to increase the session timeout time while using DBeaver or DbVisualizer to execute a SQL query? Specifically, how can I specify parameters during the connection to extend the session timeout?
I am not sure if this is a bug. I have seen others mention on URL that this approach works, but it does not work for me with the latest JDBC driver.
The text was updated successfully, but these errors were encountered: