Hi, This ticket is created for support of internal connection pooling, i.e. Ignite's implementation. As for now, you can use external connection pooling providers, like DBCP or c3p0. Please let us know if you will have any problems with that.
Evgenii пт, 9 нояб. 2018 г. в 0:42, kcheng.mvp <kcheng....@gmail.com>: > > know that the coming release (2.7) support > > JDBC: > * Implemented DataSource interface for thin driver > > > and there is a jira about the connection pool > > https://issues.apache.org/jira/browse/IGNITE-6145 > > it comments as below > > W have to support connection pool to JDBC compliance. > At the very least we must test ourselves with well-known pooling providers > (DBCP, c3p0). > This is blocked by IGNITE-6140 > > and I found https://issues.apache.org/jira/browse/IGNITE-6140 is fixed for > 2.7 > > not sure I can use jdbc thin drive with pooling providers (DBCP, c3p0) or > not? > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >