Hello! Are you sure that you are not using the same connection from two threads concurrently? Ignite thin connections are non-thread-safe.
Regards, -- Ilya Kasnacheev чт, 12 мар. 2020 г. в 11:47, yangjiajun <1371549...@qq.com>: > Hello. > > I get a strange exception while test ignite 2.8 in our test env.I get > following exception when I set lazy = true to run our tasks.The tasks do > jdbc selects and insert the result to others ignite tables.The tasks are > async.The exception throws when my code fetches 1024 rows.Such tasks works > well in ignite 2.7.And it also works well when I set lazy = false in ignite > 2.8. > > This is the exception in client: > java.sql.SQLException: General error: > "java.lang.IllegalMonitorStateException: attempt to unlock read lock, not > locked by current thread" [50000-197] > at > > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:901) > at > > org.apache.ignite.internal.jdbc.thin.JdbcThinResultSet.next(JdbcThinResultSet.java:206) > at > com.zaxxer.hikari.pool.HikariProxyResultSet.next(HikariProxyResultSet.java) > ..... > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > > The log in server: > ignite-369ae417.rar > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2059/ignite-369ae417.rar> > > > Unfortunately,I still can't make a simple reproducer in my locl env.Do u > have any ideas about such exception? > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
