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(
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/
The above idea did not work. The ignite setup is as follows/
Ignite 2.8.1
Hikari 3.4.5
Java 1.8
Spring JdbcTemplate
Apache ignite is in Azure K8S cluster, and the service is being exposed as
a Azure internal load balancer.
The api works well for some time, (*till * *1 hour of restart*), after
Hi,
I truly appreciated the support we are getting from the community.
As of now we don't have a re-producer, The above issue basically comes once
in a while.
The server is up and running, *Note*: The ignite cluster has been installed
in azure kubernetes cluster as statefulset pods.
We have
Hello!
Are you sure that the Ignite cluster is in fact up? :)
If it is, maybe your usage patterns of this pool somehow assign the
connection to two different threads, which try to do queries in parallel.
In theory, this is what connection pools are explicitly created to avoid,
but maybe there's
I wasn't able to reproduce that hurriedly. What Hikari settings do you have?
Maybe you have a reproducer?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Please find details below
Java - 1.8
Hikari - 3.4.1
Ignite - 2.6.0
SSL Enabled - false
Thanks,
Sanjaya
On Mon, Nov 2, 2020 at 8:11 PM Vladimir Pligin wrote:
> Hi,
>
> What java version do you use? What about Hikari & Ignite versions? Do you
> have SSL enabled?
>
>
>
> --
> Sent from:
Hi,
What java version do you use? What about Hikari & Ignite versions? Do you
have SSL enabled?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi All,
we are trying to use HIkari connection pooling with ignite JdbcThinDriver.
we are facing issue as
Any idea what is the supported connection pooling mechanism work with
IgniteThinDriver
ERROR LOG
==
WARN com.zaxxer.hikari.pool.ProxyConnection.157 sm-event-consumer
