}
AND DURABLE_WRITES = true
comment = 'Cache test'
AND read_repair_chance = 0.2
--
Tobias Eriksson
Chief Architect Research – CTO Office
Qvantel Sweden AB
Tel; +46 768 832453
e-mail; tobias.eriks...@qvantel.com<mailto:tobias.eriks...@qvantel.com>
n.java:288)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:398)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1273)
... 16 more
--
Tobias Eriksson
Chief Architect Research –
fixed in latest one?
I see related fix inclueded in upcoming 2.3 version.
See IGNITE-5897 [1] issue. It is unobvious, but this fix session init\end
logic, so session should be closed in proper way.
[1] https://issues.apache.org/jira/browse/IGNITE-5897
On Wed, Oct 25, 2017 at 11:13 AM, Tobias
Hi
Sorry did not include the context when I replied
Has anyone been able to resolve this problem, cause I have it too on and
off
In fact it sometimes happens just like that, e.g. I have been running my
Ignite client and then stop it, and then it takes a while and run it again,
and all by a
Hi
Did you ever resolve this problem, cause I have it too on and off
In fact it sometimes happens just like that, e.g. I have been running my
Ignite client and then stop it, and then it takes a while and run it again,
and all by a sudden this error shows up. An that is the first thing that
may have used
a PreparedStatement that was created with another Cluster instance.
--
Tobias Eriksson
Chief Architect Research – CTO Office
Qvantel Sweden AB
Tel; +46 768 832453
e-mail; tobias.eriks...@qvantel.com<mailto:tobias.eriks...@qvantel.com>
