I've reached out to some of the team who are more familiar with the Java ecosystem. JNI comes with certain performance penalties so generally it could be a bad idea unless you have enough logic to overcome the overhead. It might be worth investigatin...
Hi rlukas. We have not heard from the author in regards to this community driver, and looking at the updates and their age I think it is safe to assume that this driver does not support 5.x
There is no limit enforced by the drivers themselves. However the server you are connecting to will have a limit. The server default is 400 (which we consider high). It can be configured with
server.bolt.thread_pool_max_size
Yes adjusting the idle timeout would help. An alternative is to reduce the number of idle connections allowed in the pool. This latter option may lead to an overhead if the figure is too low as new connections will being created more than they need t...
The results and transactions make use of the connection, they have a different 'lifecycle' from the connection.
The connection is not closed when it is no longer in use by a session. It is returned to the connection pool that the driver maintains. Th...
