Re: IgniteCheckedException: Failed to validate cache configuration. Cache store factory is not s erializable.

Is there any solutions? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

IgniteCheckedException: Failed to validate cache configuration. Cache store factory is not s erializable.

Dear Master Ignite, i have exception "IgniteCheckedException: Failed to validate cache configuration. Cache store factory is not s erializable.". *Here is my code:* /** * */ package com.sybase365.mobiliser.custom.btpn.brand.ignite.custom.config; import java.io.Serializable; import

Re: SQL Transactional Support for Commit and rollback operation.

Dear Ignite Masters, Yes, i also need this features. I hope it will be release soon. I hope.. :) I have to pending my project 'mirgate oracle to ignite', cause of this. Thanks, Rizal -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

Hi Amir, How to registered Ignite's Spring Transaction Manager? Would you mind share your code... Thanks for your help Amir -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

Hi Evgenii , Yes i have try that. Without Spring Transaction. private int sequenceManual(String seqName) { int seq = 0; Query query; try { em.getTransaction().begin(); query = this.em.createNativeQuery("UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + " + INCREMENT + " WHERE SEQ_NAME

No transaction is currently active || Not allowed to create transaction on shared EntityManager - use Spring transactions or EJB CMT instead

Hi, First of all, yes I know Apache Ignite not support SQL Transaction. I hope this is not showstopper of my POC. I`m here to find another way. 1. I have function for update sequence table. private int sequenceManual(String seqName) { int seq = 0; Query query; try {

Re: Data lost when primary nodes down.

Hi Denis, Would you mind clarification my statement? I'm a little bit confuse with primary and backup nodes. And where the data is stored. Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

CacheWriterException: Failed to write entry to database

Hi, Some one please help me. It takes my time to figured this out. I got this error. It is happen when insert/update/delete operation. ignite-4c6985f2.log Here is my cluster configuration: IgniteConfiguration

Re: Data lost when primary nodes down.

Hi Denis, Thanks for your reply. > You didn't configure any backups for your cache, so, there is only one > node for every key in the cluster. In order to configure backups for cache, use CacheConfiguration.setBackups(int) method. If i have 3 nodes server, do i have to set up which is the

Data lost when primary nodes down.

Hi, I have experiment create 2nodes server. (IP: 10.5.42.95 and 10.5.42.96) With this Ignite Configuration: IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setIgniteInstanceName("BrandCluster"); TcpDiscoveryVmIpFinder ipFinder = new

Re: Migrating from Oracle to Apache Ignite.

Hi Ilya, Thanks for your reply. It is solved now, our cluster has distributed the data. And from Log Node, it is show 3 server. "[09:45:33] Topology snapshot [ver=9, servers=1, clients=0, CPUs=8, heap=0.77GB] [09:47:15] Topology snapshot [ver=10, servers=2, clients=0, CPUs=12, heap=1.8GB]

Re: Migrating from Oracle to Apache Ignite.

Hi Andrew, Thanks for your reply. Hope the ticket will be on 2.4 Next question about replication. I have 3 node server with different machine/ip. How ignite replicate/distribution data between them? Whereas my application only access into one node. Please let me know if there something I

Migrating from Oracle to Apache Ignite.

Hi, I have a project/poc, about migrating database oracle into in memory apache ignite. First of all, this is my topology. in case image not showing: https://ibb.co/cbi5cR I have done this thing: 1. Create node

Re: JDBC thin client load balancing and failover support

Yes it is. I can do put some logic to re-route to another address if primary node is down. But I think this is not solution.. Btw, this is another question for me. How about the load-balancer? Currently i have 3 VM (3 ip address). Which will be used as 3 cluster ignite. Behind that, i have

Re: JDBC thin client load balancing and failover support

Hi Val, According to this ticket 'IGNITE-7029'. How long it will be *Live*? At least tell me the estimated time? Because I have the same problem, about failover and Jdbc thin can access multiple Node (IP Address). And I need to go to POC. regards, -Rizal -- Sent from:

XML Format for Expiry Policies

Hi all, Would you mind to create xml format for this java syntax. https://apacheignite.readme.io/v2.3/docs/expiry-policies cfg.setExpiryPolicyFactory(CreatedExpiryPolicy.factoryOf(Duration.ONE_MINUTE)); thanks for your help. regards. -- Sent from: