Issue with concurrent queries sent to ClickHouse | DBeaver version 25.x

[andreyosadchuktccenter]

I have lately upgraded DBeaver version from 24.x to 25.1.3/ 25.1.4 and faced an issue with running concurrent queries.

Steps to reproduce:

1. Run a query in one tab that lasts for a while.
2. Run a query in another tab. The following error gets thrown:

SQL Error [22000]: Code: 373. DB::Exception: <Unreadable error message> (transport error: 500)

org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error [22000]: Code: 373. DB::Exception: <Unreadable error message> (transport error: 500) at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:130) at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeStatement(SQLQueryJob.java:657) at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.lambda$2(SQLQueryJob.java:550) at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:189) at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.executeSingleQuery(SQLQueryJob.java:569) at org.jkiss.dbeaver.ui.editors.sql.execute.SQLQueryJob.extractData(SQLQueryJob.java:1043) at org.jkiss.dbeaver.ui.editors.sql.SQLEditor$QueryResultsContainer.readData(SQLEditor.java:4552) at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.lambda$0(ResultSetJobDataRead.java:128) at org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:189) at org.jkiss.dbeaver.ui.controls.resultset.ResultSetJobDataRead.run(ResultSetJobDataRead.java:126) at org.jkiss.dbeaver.ui.controls.resultset.ResultSetViewer$ResultSetDataPumpJob.run(ResultSetViewer.java:5161) at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:119) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) Caused by: java.sql.SQLException: Code: 373. DB::Exception: <Unreadable error message> (transport error: 500) at com.clickhouse.jdbc.internal.ExceptionUtils.toSqlState(ExceptionUtils.java:67) at com.clickhouse.jdbc.internal.ExceptionUtils.toSqlState(ExceptionUtils.java:42) at com.clickhouse.jdbc.StatementImpl.executeQueryImpl(StatementImpl.java:208) at com.clickhouse.jdbc.StatementImpl.executeImpl(StatementImpl.java:354) at com.clickhouse.jdbc.StatementImpl.execute(StatementImpl.java:348) at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:344) at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:128) ... 12 more Caused by: com.clickhouse.client.api.ServerException: Code: 373. DB::Exception: <Unreadable error message> (transport error: 500) at com.clickhouse.client.api.internal.HttpAPIClientHelper.readError(HttpAPIClientHelper.java:374) at com.clickhouse.client.api.internal.HttpAPIClientHelper.executeRequest(HttpAPIClientHelper.java:426) at com.clickhouse.client.api.Client.lambda$query$10(Client.java:1727) at com.clickhouse.client.api.Client.runAsyncOperation(Client.java:2156) at com.clickhouse.client.api.Client.query(Client.java:1770) at com.clickhouse.client.api.Client.query(Client.java:1671) at com.clickhouse.jdbc.StatementImpl.executeQueryImpl(StatementImpl.java:194) ... 16 more

[Destrolaric]

Hi, could you create an issue in https://github.com/dbeaver/dbeaver/issues with the mentioned description?

[nail]

I was facing the same problem and the solution (or workaround) was to edit the clickhouse connection -> SQL Editor -> Check the top box to allow connection-specific settings -> change the "Open separate connection for each editor" to "Always" (or do it globally instead of just for the clickhouse connection)

[andreyosadchuktccenter]

Hi @nail ,
It helps only partly. In the previous versions it was possible to run unlimited number of concurrent queries regardless of their execution status in each instance.

However, now if one of them is being cancelled (canceled in DBeaver UI, but for some reason is still being processed on the DBMS side), then new queries end with the mentioned error.

Another example of the issue is when a user opens many tables by clicking them through the Database Navigator. Since the table data preview takes some time, the subsequent queries run before the previous ones end. This triggers an error.