Lucky, If it's possible, that this code is executed cuncurrently, then you need to add additional synchronization. Otherwise correct work of JDBC driver is not guaranteed.
Denis On Thu, Nov 30, 2017, 09:10 Lucky <[email protected]> wrote: > 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 > >> >>>
