We solved the problem by removing the complete hikari connection pooling mechanism.
Instead we use IgniteJdbcThinDataSource ( https://apacheignite-sql.readme.io/docs/jdbc-driver) , with appropriate client connector configuration( https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setClientConnectorConfiguration-org.apache.ignite.configuration.ClientConnectorConfiguration- ) After doing a few hit and trials, we concluded ignite does not require connection pooling in the client side (like we do in RDBMS) , instead let the Ignite server handle the SQL queries, by providing appropriate client connection details. On Fri, Nov 6, 2020 at 7:01 PM Vladimir Pligin <[email protected]> wrote: > In general it should be ok to use connection pooling with Ignite. Is your > network ok? It look like a connection is being closed because of network > issues. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
