Hello Ilya I do have the PERSON2 cache. Here is the snippet for the cache configuration. I don't have any issue with this configuration if I don't enable native persistence.
<property name="cacheConfiguration"> <list> <bean class="org.apache.ignite.configuration.CacheConfiguration"> <property name="name" value="PERSON2"/> <property name="cacheMode" value="PARTITIONED"/> <property name="atomicityMode" value="ATOMIC"/> <property name="writeSynchronizationMode" value="FULL_SYNC"/> <!-- Configure type metadata to enable queries. --> <property name="queryEntities"> <list> <bean class="org.apache.ignite.cache.QueryEntity" On Mon, Jan 20, 2020 at 10:40 AM Ilya Kasnacheev <[email protected]> wrote: > Hello! > > Maybe you don't have PERSON2 cache? :) > > Regards, > -- > Ilya Kasnacheev > > > пн, 20 янв. 2020 г. в 02:47, narges saleh <[email protected]>: > >> Hi All >> >> I am using JDBC connection for inserting data into caches specified in my >> config file (via query entities). If I don't enable native persistence, >> everything works fine and I can insert the data into cache/table and query >> the cache/table. But if I enable native persistence, the client dies as >> soon it attempts to create the JDBC connection, using the configuration >> file, with this error: >> >> SQLException: Client is invalid. Probably cache name is wrong. >> >> The connection command is this: >> >> Connection conn = DriverManager.getConnection( >> "jdbc:ignite:cfg://cache=PERSON2:streaming=true:streamingFlushFrequency= >> 2000@file:///opt/ignite/config/query-entity-store.xml"); >> >> Any idea what could I be doing wrong? >> >> thanks. >> >
