vsuslov wrote > Hi, we use an application in that the iBatis engine is hardcoded and we > can't to get rid of sql queries unfortunately. While we were testing the > application, we got an exception that follows. > We got it after a long time. Our queries were getting slower and slower. I > tested it on Ignite 1.1.3 and it was much faster but now I'm trying Ignite > 1.3.3 and don't know why it could be slower. > Btw I got the exception on 1.1.3 too but simultaneusly I got out of memory > error.On a local machine I'm using swap properties with eviction and it's > only choice for "lots of" data otherwise my computer dies. > Also I'm using one node but I got the exception even while I was testing > the application on two servers with two nodes with RAM 16GB of each > server. The application is OLTP-type and I know that sql is bad choice but > we can't rid of it now > > javax.cache.CacheException: Failed to run reduce query locally. > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:556) > at > org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$2.iterator(IgniteH2Indexing.java:777) > at > org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:59) > .......... > Caused by: javax.cache.CacheException: Failed to run map query remotely. > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:513) > ... 22 more > Caused by: javax.cache.CacheException: Failed to execute map query on the > node: e24e6068-6e45-4dea-978e-0ab4153ad21d, class > org.apache.ignite.IgniteException:Failed to set schema for DB connection > for thread [schema=EXECUTION] > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:212) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:202) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:183) > at > org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.onMessage(GridReduceQueryExecutor.java:139) > at > org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:1753) > at > org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:764) > at > org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:59) > at > org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:727) > ... 3 more
Hi Vadim, I believe there should be an exception with the root cause in one of the server node logs. Can you check this? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/H2-exception-lots-of-queries-tp1190p1195.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
