Hibernate connection inspite of jdbc?

Given below load method of cachejdbcpersonstore. this is done using preparedstatement n resultset. I want to implement the same using hibernate n hql query how to do this ? and what is CacheStoreSession ? where to use the same if i want to implement using hibernate by replacing this Connection c

Re: C++ Client for SQL Queries

Thanks Vladimir. I did have a look at the URLs, and also your examples in git hub. I am using the organization.h in the git hub and want to just run a SQL query on a cache with Organization objects. I get this error - Indexing is disabled for cache: myCache. Use setIndexedTypes or setTypeMetadata

Re: C++ Client for SQL Queries

Hi Arthi, Please have a look at Ignite C++ documentation about indexes and serialization: https://apacheignite-cpp.readme.io/docs/sql-queries https://apacheignite-cpp.readme.io/docs/serialization Let me know if you have any further questions. We will add more SQL examples for C++ in the nearest

Re: java.lang.IllegalStateException: Cache has been stopped

following is the detailed log, thank you for help me to check it. 2016-03-04 20:39:26 STDIO [ERROR] Mar 04, 2016 8:39:26 PM org.apache.ignite.logger.java.JavaLogger error SEVERE: Failed to send local partition map to node [node=TcpDiscoveryNode [id=6701f10e-8319-47ac-99b2-3521cfaf91ca, addrs=[127.

C++ Client for SQL Queries

Hi, We need to get a C++ client to run SQL queries on caches built from our server ignite components. I am not seeing an example for this in the GIT HUB, can you please help? I need to understand how the objects are defined for SQL queries (query entities or annotations) and how they are indexed i

Re: java.lang.IllegalStateException: Cache has been stopped

Anyway, I would check the logs. Are there any errors? Did the topology change? Was the node stopped? If you upload your log files somewhere, I will take a look. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/java-lang-IllegalStateException-Cache-has-been-

Re: visor command line authentication.

Start command essentially connects to the remote host using SSH and executes ignite.sh script there. Username and password here are for SSH connection. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/visor-command-line-authentication-tp3395p3405.html Sent f

Re: Inserts stalled by write-behind process

Agree with Valentin. One other thing you may wish to check is whether you are doing a bulk insert to the database, or multiple individual inserts. Bulk insert should perform better, of course. D. On Tue, Mar 8, 2016 at 4:50 PM, vkulichenko wrote: > Hi, > > You're right, write-behind store has a

Re: visor command line authentication.

Sorry I wasn't clear earlier. I would like to start an ignite node on a remote host that's part of my discoveryspi ip address list. So, in order to use the command something like at visor cmd visor> start -h=myhostip -uname=username -pw=password -n=2 I would like to know that username and passwo

Re: java.lang.IllegalStateException: Cache has been stopped

No, I only do cache.get from the same server node. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/java-lang-IllegalStateException-Cache-has-been-stopped-tp3389p3402.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: visor command line authentication.

Hi krishna, Can you please properly subscribe to the mailing list so that the community receives email notifications? Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 krishna wrote > Hello, I am a beginner to ignite. > Can some o

Re: Unable to cache beyond RAM memory. Help me PLease!!!

Hi Bhargav, Are you sure that 4GB is enough for your data? How many entries do you have and what is the average size of each entry in bytes? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unable-to-cache-beyond-RAM-memory-Help-me-PLease-tp3366p3400.html S

Re: Inserts stalled by write-behind process

Hi, You're right, write-behind store has a back pressure mechanism that starts to update DB synchronously if the queue is too long. Otherwise you will most likely eventually get out of memory error. The backlog size is controlled by CacheConfiguration.setWriteBehindFlushSize() property. When this

Re: java.lang.IllegalStateException: Cache has been stopped

Hi, Are you doing cache.get from a client node? If so, is it possible that it was disconnected from topology and then reconnected back? There are scenarios when you can get this exception after this happens [1]. I would start with checking if there are any exceptions and/or warnings in the logs.

Re: Continuously running jobs

Hi, Sorry, somehow I missed this question. Sounds like Ignite compute grid should be perfect for your task. Ignite load balances the jobs within the cluster automatically, with several load balancing policies available, so you should be able to simply unicast or broadcast closures and have them e

Re: Continuously running jobs

Was I not clear enough? Did I ask for something stupid?

Re: Atomicity mode and read-after-write consistency

Hi, Consistency between nodes is guaranteed in ATOMIC mode, however, the read-after-write guarantee is met in the following cases: - cache write synchronization mode is FULL_SYNC. In this mode cache.put() will not return control until all data nodes (primary and backup) responsible for the data a

Re: A Question About Behavior

We were directly Manipulating the Cache.Entry and it was reflecting directly in the H2 Indexes.. Not sure if it's desired behavior or not.. But a definite Gotcha To fix this we just call VALUE = ingintecache.get(KEY) to retrieve the value rather than getting it directly from the entry (VALUE =

Atomicity mode and read-after-write consistency

I have a question about consistency between nodes in an ignite cluster. We are writing entries into an ignite cache on one node and reading the same entry on another node just 1 second later but we observe that this second node does not yet contain the entry. Is this normal behaviour? Note that we

Inserts stalled by write-behind process

We are currently using an ignite setup with caches with very large offheap sizes (10GB+) and in these caches we are inserting entries of roughly 30 kB. We flush the entries to disk every minute using write-behind. What we observe is that after a while, the inserts of new entries into the cache see