Denis,
I used java code,just like this:
Connection conn = getConn();
PreparedStatement stmt = conn.prepareStatement(sql);
ResultSet rs = stmt.executeQuery();
public Connection getConn() throws SQLException{
if (conn==null || conn.isClosed()){
try {
Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
conn =
DriverManager.getConnection("jdbc:ignite:thin://192.168.1.2?distributedJoins=true");
} catch (Exception e) {
logger.error("IgniteSererFacade getConn error === ",e);
}
}
return conn;
}
Yes, I only used one connection.
Because there will execute many times in one operation. Sometimes there
will have 30 times.
If I create a JDBC connection every time, the performance can not be
accepted.
This problem did not reproduce if use DBeaver.
Also I have say before, that If I exit the system,And relogin again, it is
normal.
Thank you very much.
At 2017-11-29 18:37:33, "Denis Mekhanikov" <[email protected]> wrote:
Lucky,
What tool are you using to access Ignite over JDBC? Does this problem
reproduce, if you use DBeaver, for example?
As Taras said, looks like the same JDBC connection is used concurrently.
Denis
