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 <chetan.v.ya...@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. >
