You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "Chetan.V.Yadav" <Ch...@target.com> on 2016/11/01 20:08:46 UTC
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
I have attached gradle file along with my config xml.
On 11/1/16, 11:05 PM, "Sergej Sidorov" <se...@gmail.com> wrote:
Hi chevy!
I suppose that the issue in your configuration. Could you please provide
your pom.xml and mpm-ignite.xml?
Thanks,
Sergej
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8651.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by chevy <ch...@target.com>.
I went to local gradle repo and manually deleted other h2 versions. It’s
working now.
I have one more query – is there a way I can make ‘ignite-http-rest’ work
with spring-boot? Last time when I checked with one of Ignite dev they
mentioned that I can’t use it with boot. Without rest-api, I need to create
a JDBC connection and fire up my own rest-api which has higher response time
compared to ignite’s rest api.
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8773.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by vkulichenko <va...@gmail.com>.
Hi,
You can do Ignition.setClientMode(true) before Ignition.start(..). This will
switch started node to client mode.
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8754.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by chevy <ch...@target.com>.
I went to local gradle repo and manually deleted other h2 versions. It’s working now. Thanks for looking into it.
I have one more query – is there a way I can make ‘ignite-http-rest’ work with spring-boot? Last time when I checked with one of Ignite dev they mentioned that I can’t use it with boot. Without rest-api, I need to create a JDBC connection and fire up my own rest-api which has higher response time compared to ignite’s rest api.
--
Regards,
Chetan.
From: "Sergi Vladykin [via Apache Ignite Users]" <ml...@n6.nabble.com>
Date: Thursday, November 3, 2016 at 3:13 PM
To: "Chetan.V.Yadav" <Ch...@target.com>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Ok, then please check your effective classpath:
System.out.println(System.getProperty("java.class.path"));
Also you can check where H2 classes come from:
System.out.println(org.h2.Driver.class.getProtectionDomain().getCodeSource().getLocation());
In the end you must have in classpath only h2-1.4.191.jar and no other versions.
Sergi
2016-11-03 9:13 GMT+03:00 chevy <[hidden email]<file://localhost/user/SendEmail.jtp%3Ftype=node&node=8677&i=0>>:
There are no remote nodes deployed yet. I am still in dev phase so trying to start ignite locally with just one instance from the code itself.
--
Regards,
Chetan.
From: "Sergi Vladykin [via Apache Ignite Users]" <ml-node+[hidden email]<http:///user/SendEmail.jtp?type=node&node=8675&i=0>>
Date: Thursday, November 3, 2016 at 12:50 AM
To: "Chetan.V.Yadav" <[hidden email]<http:///user/SendEmail.jtp?type=node&node=8675&i=1>>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Dependency com.h2database:h2:1.4.191 is correct. You definitely have some other H2 version in classpath (at least on remote node). Note that you must have correct H2 version in classpath on all the cluster nodes.
BTW, can you please post exception stack trace from remote node?
Sergi
2016-11-02 21:41 GMT+03:00 chevy <[hidden email]>:
I see only one dependency which is coming from ignite-indexing jar. Please refer dependency chain below –
\--- org.apache.ignite:ignite-indexing:1.7.0
+--- org.apache.ignite:ignite-core:1.7.0 (*)
+--- commons-codec:commons-codec:1.6 -> 1.10
+--- org.apache.lucene:lucene-core:3.5.0
\--- com.h2database:h2:1.4.191
Also, I am getting errors with both versions of h2.
--
Regards,
Chetan.
From: "Sergi Vladykin [via Apache Ignite Users]" <ml-node+[hidden email]<http:///user/SendEmail.jtp?type=node&node=8672&i=0>>
Date: Wednesday, November 2, 2016 at 11:26 PM
To: "Chetan.V.Yadav" <[hidden email]<http:///user/SendEmail.jtp?type=node&node=8672&i=1>>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
The problem here is that you have a wrong H2 version in classpath. Most probably this wrong transitive dependency comes from Spring Boot, you need to exclude it.
Sergi
2016-11-02 20:35 GMT+03:00 chevy <[hidden email]>:
It works perfectly without spring-boot (previously tested) but I need to go with spring-boot as business logic needs faster execution using boot features. Is there any workaround with which I can fix this problem?
--
Regards,
Chetan.
From: "Sergej Sidorov [via Apache Ignite Users]" <ml-node+[hidden email]<http:///user/SendEmail.jtp?type=node&node=8669&i=0>>
Date: Wednesday, November 2, 2016 at 9:43 PM
To: "Chetan.V.Yadav" <[hidden email]<http:///user/SendEmail.jtp?type=node&node=8669&i=1>>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Do your server node is also under spring boot or it is plain ignite assembly?
I did the following:
1. Start server node from regular ignite assembly
2. Run client with your configuration (build.gradle, mpm-ignite.xml)
All worked correct with changes described in my previous message.
Of course, I was still added cache configuration:
<property name="cacheConfiguration">
<list>
<bean
class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="Company" />
<property name="atomicityMode" value="ATOMIC" />
<property name="backups" value="1" />
<property name="indexedTypes">
<list>
<value>java.lang.String</value>
<value>org.ignite.example.Company</value>
</list>
</property>
</bean>
</list>
</property>
I guess it is still issue with dependencies. Check your project dependency graph.
Sergej
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
________________________________
View this message in context: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API<http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8669.html>
Sent from the Apache Ignite Users mailing list archive<http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8670.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
________________________________
View this message in context: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API<http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8672.html>
Sent from the Apache Ignite Users mailing list archive<http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8673.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
________________________________
View this message in context: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API<http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8675.html>
Sent from the Apache Ignite Users mailing list archive<http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8677.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8648&code=Y2hldGFuLnYueWFkYXZAdGFyZ2V0LmNvbXw4NjQ4fC02OTIwMTYzODA=>.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8683.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by chevy <ch...@target.com>.
I am starting my server node within my boot app[1]. Both my client and server
nodes start from same code but I will get the service part with starts
client out of it later. How can I not start ignite server and still manage
to use same config in my external server node? (bold part below).
[1] - /* Initialize cache configuration */
cacheCfg.setName("salesCache");
cacheCfg.setCacheMode(CacheMode.REPLICATED);
cacheCfg.setSwapEnabled(false);
cacheCfg.setOffHeapMaxMemory(0);
cacheCfg.setCopyOnRead(false);
cacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC);
cacheCfg.setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.CLOCK);
cacheCfg.setIndexedTypes(Integer.class, SalesModel.class);
/* Start Ignite node. */
*Ignite ignite = Ignition.start("src/main/resources/mpm-ignite.xml");*
try (IgniteCache<Integer, SalesModel> cache =
ignite.getOrCreateCache(cacheCfg)) {
if (ignite.cluster().forDataNodes(cache.getName()).nodes().isEmpty()) {
System.out.println();
System.out.println(">>> requires remote cache nodes to be started.");
System.out.println(">>> Please start at least 1 remote cache node.");
System.out.println();
return;
}
// Put created data entries to cache.
cache.putAll(salesFinalMap);
} catch (Exception e) {
ignite.destroyCache("salesCache");
throw e;
} finally {
// Delete cache with its content completely.
// ignite.destroyCache("testCache");
}
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8684.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by Sergej Sidorov <se...@gmail.com>.
Hi!
That part of the code [1] starts Ignite client's node. In order to client's
node is working, sever node is required (instance of Ignite with
clientMode(false)). Do you run both those node in the same process or you
run separate spring boot instance?
Please note that in order to start server node it is not required to write
the code. So that you need to download the package from the link below [2]
and run it with your configuration.
Could you share the entire sample project?
[1] Connection conn = DriverManager.getConnection("jdbc:ignite:cfg://....")
[2] https://ignite.apache.org/download.cgi
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8681.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Posted by Sergi Vladykin <se...@gmail.com>.
Ok, then please check your effective classpath:
System.out.println(System.getProperty("java.class.path"));
Also you can check where H2 classes come from:
System.out.println(org.h2.Driver.class.getProtectionDomain().getCodeSource().getLocation());
In the end you must have in classpath only h2-1.4.191.jar and no other
versions.
Sergi
2016-11-03 9:13 GMT+03:00 chevy <ch...@target.com>:
> There are no remote nodes deployed yet. I am still in dev phase so trying
> to start ignite locally with just one instance from the code itself.
>
>
>
> --
>
> Regards,
>
> Chetan.
>
>
>
> *From: *"Sergi Vladykin [via Apache Ignite Users]" <ml-node+[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8675&i=0>>
> *Date: *Thursday, November 3, 2016 at 12:50 AM
> *To: *"Chetan.V.Yadav" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8675&i=1>>
> *Subject: *Re: [EXTERNAL] Re: Exception while trying to access cache via
> JDBC API
>
>
>
> Dependency com.h2database:h2:1.4.191 is correct. You definitely have some
> other H2 version in classpath (at least on remote node). Note that you must
> have correct H2 version in classpath on all the cluster nodes.
>
>
>
> BTW, can you please post exception stack trace from remote node?
>
>
>
> Sergi
>
>
>
> 2016-11-02 21:41 GMT+03:00 chevy <[hidden email]>:
>
> I see only one dependency which is coming from ignite-indexing jar. Please
> refer dependency chain below –
>
>
>
> \--- org.apache.ignite:ignite-indexing:1.7.0
>
> +--- org.apache.ignite:ignite-core:1.7.0 (*)
>
> +--- commons-codec:commons-codec:1.6 -> 1.10
>
> +--- org.apache.lucene:lucene-core:3.5.0
>
> \--- com.h2database:h2:1.4.191
>
>
>
> Also, I am getting errors with both versions of h2.
>
>
>
> --
>
> Regards,
>
> Chetan.
>
>
>
> *From: *"Sergi Vladykin [via Apache Ignite Users]" <ml-node+[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8672&i=0>>
> *Date: *Wednesday, November 2, 2016 at 11:26 PM
> *To: *"Chetan.V.Yadav" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8672&i=1>>
> *Subject: *Re: [EXTERNAL] Re: Exception while trying to access cache via
> JDBC API
>
>
>
> The problem here is that you have a wrong H2 version in classpath. Most
> probably this wrong transitive dependency comes from Spring Boot, you need
> to exclude it.
>
>
>
> Sergi
>
>
>
> 2016-11-02 20:35 GMT+03:00 chevy <[hidden email]>:
>
> It works perfectly without spring-boot (previously tested) but I need to
> go with spring-boot as business logic needs faster execution using boot
> features. Is there any workaround with which I can fix this problem?
>
>
>
> --
>
> Regards,
>
> Chetan.
>
>
>
> *From: *"Sergej Sidorov [via Apache Ignite Users]" <ml-node+[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8669&i=0>>
> *Date: *Wednesday, November 2, 2016 at 9:43 PM
> *To: *"Chetan.V.Yadav" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8669&i=1>>
> *Subject: *Re: [EXTERNAL] Re: Exception while trying to access cache via
> JDBC API
>
>
>
> Do your server node is also under spring boot or it is plain ignite
> assembly?
> I did the following:
> 1. Start server node from regular ignite assembly
> 2. Run client with your configuration (build.gradle, mpm-ignite.xml)
> All worked correct with changes described in my previous message.
> Of course, I was still added cache configuration:
>
> <property name="cacheConfiguration">
> <list>
>
> <bean
> class="org.apache.ignite.configuration.
> CacheConfiguration">
> <property name="name" value="Company" />
> <property name="atomicityMode" value="ATOMIC" />
> <property name="backups" value="1" />
> <property name="indexedTypes">
> <list>
> <value>java.lang.String</value>
> <value>org.ignite.example.
> Company</value>
> </list>
> </property>
> </bean>
> </list>
> </property>
>
> I guess it is still issue with dependencies. Check your project dependency
> graph.
>
> Sergej
> ------------------------------
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
> http://apache-ignite-users.70518.x6.nabble.com/Exception-
> while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
>
> To unsubscribe from Exception while trying to access cache via JDBC API,
> click here.
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
> ------------------------------
>
> View this message in context: Re: [EXTERNAL] Re: Exception while trying
> to access cache via JDBC API
> <http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8669.html>
>
>
> Sent from the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>
>
>
>
> ------------------------------
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
> http://apache-ignite-users.70518.x6.nabble.com/Exception-
> while-trying-to-access-cache-via-JDBC-API-tp8648p8670.html
>
> To unsubscribe from Exception while trying to access cache via JDBC API,
> click here.
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
> ------------------------------
>
> View this message in context: Re: [EXTERNAL] Re: Exception while trying
> to access cache via JDBC API
> <http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8672.html>
> Sent from the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>
>
>
>
> ------------------------------
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
> http://apache-ignite-users.70518.x6.nabble.com/Exception-
> while-trying-to-access-cache-via-JDBC-API-tp8648p8673.html
>
> To unsubscribe from Exception while trying to access cache via JDBC API, click
> here.
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> ------------------------------
> View this message in context: Re: [EXTERNAL] Re: Exception while trying
> to access cache via JDBC API
> <http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8675.html>
> Sent from the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by chevy <ch...@target.com>.
There are no remote nodes deployed yet. I am still in dev phase so trying to start ignite locally with just one instance from the code itself.
--
Regards,
Chetan.
From: "Sergi Vladykin [via Apache Ignite Users]" <ml...@n6.nabble.com>
Date: Thursday, November 3, 2016 at 12:50 AM
To: "Chetan.V.Yadav" <Ch...@target.com>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Dependency com.h2database:h2:1.4.191 is correct. You definitely have some other H2 version in classpath (at least on remote node). Note that you must have correct H2 version in classpath on all the cluster nodes.
BTW, can you please post exception stack trace from remote node?
Sergi
2016-11-02 21:41 GMT+03:00 chevy <[hidden email]<file://localhost/user/SendEmail.jtp%3Ftype=node&node=8673&i=0>>:
I see only one dependency which is coming from ignite-indexing jar. Please refer dependency chain below –
\--- org.apache.ignite:ignite-indexing:1.7.0
+--- org.apache.ignite:ignite-core:1.7.0 (*)
+--- commons-codec:commons-codec:1.6 -> 1.10
+--- org.apache.lucene:lucene-core:3.5.0
\--- com.h2database:h2:1.4.191
Also, I am getting errors with both versions of h2.
--
Regards,
Chetan.
From: "Sergi Vladykin [via Apache Ignite Users]" <ml-node+[hidden email]<http:///user/SendEmail.jtp?type=node&node=8672&i=0>>
Date: Wednesday, November 2, 2016 at 11:26 PM
To: "Chetan.V.Yadav" <[hidden email]<http:///user/SendEmail.jtp?type=node&node=8672&i=1>>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
The problem here is that you have a wrong H2 version in classpath. Most probably this wrong transitive dependency comes from Spring Boot, you need to exclude it.
Sergi
2016-11-02 20:35 GMT+03:00 chevy <[hidden email]>:
It works perfectly without spring-boot (previously tested) but I need to go with spring-boot as business logic needs faster execution using boot features. Is there any workaround with which I can fix this problem?
--
Regards,
Chetan.
From: "Sergej Sidorov [via Apache Ignite Users]" <ml-node+[hidden email]<http:///user/SendEmail.jtp?type=node&node=8669&i=0>>
Date: Wednesday, November 2, 2016 at 9:43 PM
To: "Chetan.V.Yadav" <[hidden email]<http:///user/SendEmail.jtp?type=node&node=8669&i=1>>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Do your server node is also under spring boot or it is plain ignite assembly?
I did the following:
1. Start server node from regular ignite assembly
2. Run client with your configuration (build.gradle, mpm-ignite.xml)
All worked correct with changes described in my previous message.
Of course, I was still added cache configuration:
<property name="cacheConfiguration">
<list>
<bean
class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="Company" />
<property name="atomicityMode" value="ATOMIC" />
<property name="backups" value="1" />
<property name="indexedTypes">
<list>
<value>java.lang.String</value>
<value>org.ignite.example.Company</value>
</list>
</property>
</bean>
</list>
</property>
I guess it is still issue with dependencies. Check your project dependency graph.
Sergej
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
________________________________
View this message in context: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API<http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8669.html>
Sent from the Apache Ignite Users mailing list archive<http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8670.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
________________________________
View this message in context: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API<http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8672.html>
Sent from the Apache Ignite Users mailing list archive<http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8673.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8648&code=Y2hldGFuLnYueWFkYXZAdGFyZ2V0LmNvbXw4NjQ4fC02OTIwMTYzODA=>.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8675.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Posted by Sergi Vladykin <se...@gmail.com>.
Dependency com.h2database:h2:1.4.191 is correct. You definitely have some
other H2 version in classpath (at least on remote node). Note that you must
have correct H2 version in classpath on all the cluster nodes.
BTW, can you please post exception stack trace from remote node?
Sergi
2016-11-02 21:41 GMT+03:00 chevy <ch...@target.com>:
> I see only one dependency which is coming from ignite-indexing jar. Please
> refer dependency chain below –
>
>
>
> \--- org.apache.ignite:ignite-indexing:1.7.0
>
> +--- org.apache.ignite:ignite-core:1.7.0 (*)
>
> +--- commons-codec:commons-codec:1.6 -> 1.10
>
> +--- org.apache.lucene:lucene-core:3.5.0
>
> \--- com.h2database:h2:1.4.191
>
>
>
> Also, I am getting errors with both versions of h2.
>
>
>
> --
>
> Regards,
>
> Chetan.
>
>
>
> *From: *"Sergi Vladykin [via Apache Ignite Users]" <ml-node+[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8672&i=0>>
> *Date: *Wednesday, November 2, 2016 at 11:26 PM
> *To: *"Chetan.V.Yadav" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8672&i=1>>
> *Subject: *Re: [EXTERNAL] Re: Exception while trying to access cache via
> JDBC API
>
>
>
> The problem here is that you have a wrong H2 version in classpath. Most
> probably this wrong transitive dependency comes from Spring Boot, you need
> to exclude it.
>
>
>
> Sergi
>
>
>
> 2016-11-02 20:35 GMT+03:00 chevy <[hidden email]>:
>
> It works perfectly without spring-boot (previously tested) but I need to
> go with spring-boot as business logic needs faster execution using boot
> features. Is there any workaround with which I can fix this problem?
>
>
>
> --
>
> Regards,
>
> Chetan.
>
>
>
> *From: *"Sergej Sidorov [via Apache Ignite Users]" <ml-node+[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8669&i=0>>
> *Date: *Wednesday, November 2, 2016 at 9:43 PM
> *To: *"Chetan.V.Yadav" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8669&i=1>>
> *Subject: *Re: [EXTERNAL] Re: Exception while trying to access cache via
> JDBC API
>
>
>
> Do your server node is also under spring boot or it is plain ignite
> assembly?
> I did the following:
> 1. Start server node from regular ignite assembly
> 2. Run client with your configuration (build.gradle, mpm-ignite.xml)
> All worked correct with changes described in my previous message.
> Of course, I was still added cache configuration:
>
> <property name="cacheConfiguration">
> <list>
>
> <bean
> class="org.apache.ignite.configuration.
> CacheConfiguration">
> <property name="name" value="Company" />
> <property name="atomicityMode" value="ATOMIC" />
> <property name="backups" value="1" />
> <property name="indexedTypes">
> <list>
> <value>java.lang.String</value>
> <value>org.ignite.example.
> Company</value>
> </list>
> </property>
> </bean>
> </list>
> </property>
>
> I guess it is still issue with dependencies. Check your project dependency
> graph.
>
> Sergej
> ------------------------------
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
> http://apache-ignite-users.70518.x6.nabble.com/Exception-
> while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
>
> To unsubscribe from Exception while trying to access cache via JDBC API,
> click here.
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
> ------------------------------
>
> View this message in context: Re: [EXTERNAL] Re: Exception while trying
> to access cache via JDBC API
> <http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8669.html>
>
>
> Sent from the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>
>
>
>
> ------------------------------
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
> http://apache-ignite-users.70518.x6.nabble.com/Exception-
> while-trying-to-access-cache-via-JDBC-API-tp8648p8670.html
>
> To unsubscribe from Exception while trying to access cache via JDBC API, click
> here.
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> ------------------------------
> View this message in context: Re: [EXTERNAL] Re: Exception while trying
> to access cache via JDBC API
> <http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8672.html>
> Sent from the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by chevy <ch...@target.com>.
I see only one dependency which is coming from ignite-indexing jar. Please refer dependency chain below –
\--- org.apache.ignite:ignite-indexing:1.7.0
+--- org.apache.ignite:ignite-core:1.7.0 (*)
+--- commons-codec:commons-codec:1.6 -> 1.10
+--- org.apache.lucene:lucene-core:3.5.0
\--- com.h2database:h2:1.4.191
Also, I am getting errors with both versions of h2.
--
Regards,
Chetan.
From: "Sergi Vladykin [via Apache Ignite Users]" <ml...@n6.nabble.com>
Date: Wednesday, November 2, 2016 at 11:26 PM
To: "Chetan.V.Yadav" <Ch...@target.com>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
The problem here is that you have a wrong H2 version in classpath. Most probably this wrong transitive dependency comes from Spring Boot, you need to exclude it.
Sergi
2016-11-02 20:35 GMT+03:00 chevy <[hidden email]<file://localhost/user/SendEmail.jtp%3Ftype=node&node=8670&i=0>>:
It works perfectly without spring-boot (previously tested) but I need to go with spring-boot as business logic needs faster execution using boot features. Is there any workaround with which I can fix this problem?
--
Regards,
Chetan.
From: "Sergej Sidorov [via Apache Ignite Users]" <ml-node+[hidden email]<http:///user/SendEmail.jtp?type=node&node=8669&i=0>>
Date: Wednesday, November 2, 2016 at 9:43 PM
To: "Chetan.V.Yadav" <[hidden email]<http:///user/SendEmail.jtp?type=node&node=8669&i=1>>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Do your server node is also under spring boot or it is plain ignite assembly?
I did the following:
1. Start server node from regular ignite assembly
2. Run client with your configuration (build.gradle, mpm-ignite.xml)
All worked correct with changes described in my previous message.
Of course, I was still added cache configuration:
<property name="cacheConfiguration">
<list>
<bean
class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="Company" />
<property name="atomicityMode" value="ATOMIC" />
<property name="backups" value="1" />
<property name="indexedTypes">
<list>
<value>java.lang.String</value>
<value>org.ignite.example.Company</value>
</list>
</property>
</bean>
</list>
</property>
I guess it is still issue with dependencies. Check your project dependency graph.
Sergej
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
________________________________
View this message in context: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API<http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8669.html>
Sent from the Apache Ignite Users mailing list archive<http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8670.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8648&code=Y2hldGFuLnYueWFkYXZAdGFyZ2V0LmNvbXw4NjQ4fC02OTIwMTYzODA=>.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8672.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Posted by Sergi Vladykin <se...@gmail.com>.
The problem here is that you have a wrong H2 version in classpath. Most
probably this wrong transitive dependency comes from Spring Boot, you need
to exclude it.
Sergi
2016-11-02 20:35 GMT+03:00 chevy <ch...@target.com>:
> It works perfectly without spring-boot (previously tested) but I need to
> go with spring-boot as business logic needs faster execution using boot
> features. Is there any workaround with which I can fix this problem?
>
>
>
> --
>
> Regards,
>
> Chetan.
>
>
>
> *From: *"Sergej Sidorov [via Apache Ignite Users]" <ml-node+[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8669&i=0>>
> *Date: *Wednesday, November 2, 2016 at 9:43 PM
> *To: *"Chetan.V.Yadav" <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=8669&i=1>>
> *Subject: *Re: [EXTERNAL] Re: Exception while trying to access cache via
> JDBC API
>
>
>
> Do your server node is also under spring boot or it is plain ignite
> assembly?
> I did the following:
> 1. Start server node from regular ignite assembly
> 2. Run client with your configuration (build.gradle, mpm-ignite.xml)
> All worked correct with changes described in my previous message.
> Of course, I was still added cache configuration:
>
> <property name="cacheConfiguration">
> <list>
>
> <bean
> class="org.apache.ignite.configuration.
> CacheConfiguration">
> <property name="name" value="Company" />
> <property name="atomicityMode" value="ATOMIC" />
> <property name="backups" value="1" />
> <property name="indexedTypes">
> <list>
> <value>java.lang.String</value>
> <value>org.ignite.example.
> Company</value>
> </list>
> </property>
> </bean>
> </list>
> </property>
>
> I guess it is still issue with dependencies. Check your project dependency
> graph.
>
> Sergej
> ------------------------------
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
> http://apache-ignite-users.70518.x6.nabble.com/Exception-
> while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
>
> To unsubscribe from Exception while trying to access cache via JDBC API, click
> here.
> NAML
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> ------------------------------
> View this message in context: Re: [EXTERNAL] Re: Exception while trying
> to access cache via JDBC API
> <http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8669.html>
>
> Sent from the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by chevy <ch...@target.com>.
It works perfectly without spring-boot (previously tested) but I need to go with spring-boot as business logic needs faster execution using boot features. Is there any workaround with which I can fix this problem?
--
Regards,
Chetan.
From: "Sergej Sidorov [via Apache Ignite Users]" <ml...@n6.nabble.com>
Date: Wednesday, November 2, 2016 at 9:43 PM
To: "Chetan.V.Yadav" <Ch...@target.com>
Subject: Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC API
Do your server node is also under spring boot or it is plain ignite assembly?
I did the following:
1. Start server node from regular ignite assembly
2. Run client with your configuration (build.gradle, mpm-ignite.xml)
All worked correct with changes described in my previous message.
Of course, I was still added cache configuration:
<property name="cacheConfiguration">
<list>
<bean
class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="Company" />
<property name="atomicityMode" value="ATOMIC" />
<property name="backups" value="1" />
<property name="indexedTypes">
<list>
<value>java.lang.String</value>
<value>org.ignite.example.Company</value>
</list>
</property>
</bean>
</list>
</property>
I guess it is still issue with dependencies. Check your project dependency graph.
Sergej
________________________________
If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
To unsubscribe from Exception while trying to access cache via JDBC API, click here<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8648&code=Y2hldGFuLnYueWFkYXZAdGFyZ2V0LmNvbXw4NjQ4fC02OTIwMTYzODA=>.
NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8669.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by Sergej Sidorov <se...@gmail.com>.
Do your server node is also under spring boot or it is plain ignite assembly?
I did the following:
1. Start server node from regular ignite assembly
2. Run client with your configuration (build.gradle, mpm-ignite.xml)
All worked correct with changes described in my previous message.
Of course, I was still added cache configuration:
<property name="cacheConfiguration">
<list>
<bean
class="org.apache.ignite.configuration.CacheConfiguration">
<property name="name" value="Company" />
<property name="atomicityMode" value="ATOMIC" />
<property name="backups" value="1" />
<property name="indexedTypes">
<list>
<value>java.lang.String</value>
<value>org.ignite.example.Company</value>
</list>
</property>
</bean>
</list>
</property>
I guess it is still issue with dependencies. Check your project dependency
graph.
Sergej
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8668.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by chevy <ch...@target.com>.
There is a issue with downgrading h2 jar. I am working with spring-boot and I
had tried this earlier. It throws below exception -
[17:32:43] Ignite node stopped OK
[name=ignite-jdbc-driver-297d7d9b-ee4c-47b8-abcf-fe4812374296,
uptime=00:00:00:233]
java.sql.SQLException: Failed to query Ignite.
at
org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(JdbcStatement.java:115)
at com.target.ignite.util.IgniteJdbcApi.main(IgniteJdbcApi.java:47)
Caused by: javax.cache.CacheException: Failed to run map query remotely.
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:624)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$3.iterator(IgniteH2Indexing.java:1012)
at
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:61)
at
org.apache.ignite.internal.jdbc2.JdbcQueryTask.call(JdbcQueryTask.java:172)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(JdbcStatement.java:102)
... 1 more
Caused by: javax.cache.CacheException: Failed to execute map query on the
node: 94e3eb85-7c1a-4026-bc88-35d7bc875e50, class
java.lang.AbstractMethodError:org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$ScanIndex.getCost(Lorg/h2/engine/Session;[I[Lorg/h2/table/TableFilter;ILorg/h2/result/SortOrder;Ljava/util/HashSet;)D
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.fail(GridReduceQueryExecutor.java:277)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onFail(GridReduceQueryExecutor.java:267)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.onMessage(GridReduceQueryExecutor.java:248)
at
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$2.onMessage(GridReduceQueryExecutor.java:196)
at
org.apache.ignite.internal.managers.communication.GridIoManager$ArrayListener.onMessage(GridIoManager.java:2071)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1238)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:866)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:829)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8666.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: [EXTERNAL] Re: Exception while trying to access cache via JDBC
API
Posted by Sergej Sidorov <se...@gmail.com>.
Hi!
I reproduced exception with your configs.
I explored project dependencies and found newer version of H2 library.
The next string in build.gradle fixed exception for me:
compile group: 'com.h2database', name: 'h2', version: '1.4.191'
I'm not an expert in gradle and maybe there is more elegant solution.
Thanks,
Sergej
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Exception-while-trying-to-access-cache-via-JDBC-API-tp8648p8664.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.