Client service uses all ports about clickhouse4j

[doom369]

If you want to reuse the connection I would recommend you to use the Connection pool. Because connections are not threadsafe and managing multiple connections would be a tricky task. While connection pools keeps them keep-alive, managing them and makes access to them threadsafe.

Also, few comments regarding you code:

You don't need to make connection and prepared statement as final if you use them in try () catch, they are effectively final anyway.
You don't need to preparedStatement.clearBatch() in case preparedStatement was in try (preparedStatement) block as it will be closed and cleared by GC anyway.

[doom369]

Hello. Code in the first snippet looks correct. From what I understand - you don't use Connection Pool. Is that correct? What driver version do you use?

Also, second snippet doesn't close the connections. While first one - does.

[rado-r]

Yes first one close connection every batch insert in second one I try to reuse connections if they are not closed. Yes I don't use Connection Pool and I try clickhouse4j 1.1.1 and 1.4.1 with same results.

[doom369]

@rado-r do you use the code without try () catch in multi threaded env?

[doom369]

@rado-r I did a quick fix - https://github.com/blynkkk/clickhouse4j/releases/download/clickhouse4j-1.4.1/clickhouse4j-1.4.2-SNAPSHOT.jar

Could you please check?

[doom369]

@rado-r hello. do you have any updates? Also, what Java version do you have?

[rado-r]

@doom369 thank's for very fast response I test it and now it is fixed. I test old released version with connection pool (Hikari) but it don't releases ports too but it was only hundreds of ports. After this fix it is 0 ports. So gread job.

We use Java 8.

[doom369]

@rado-r so you used the provided build and it is fixes the issue, is that correct?

How many open connections did you saw? Were they in CLOSE_WAIT state?

[rado-r]

@doom369 yes provided build fix the issue.
Before fix I try to insert 2 billion records and connector uses all ports of docker there wasn't any free port to continue.

netstat -pnt |grep CLOSE_WAIT| wc -l
28232

[rado-r]

What do you think when it will be on maven?

[doom369]

We will try to release today. However, this situation is very strange. Because in this driver we rely on HTTPUrlConnection (while original driver relies on apache commons connection pool) in which connection pool is handled on the level of JVM. In old JVM there was a bug with non-closed connections. However, it was fixed many days ago, so now it should work. Also, on our envs (we have dozens of them) it is not the case. So it would be cool to find the actual cause.

Could you please provide also exact version of JVM and OS?

[rado-r]

It should be

OpenJDK Runtime Environment (build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)

in docker openjdk:8-jre but it is customised docker image so I'm not 100% sure.