Re: websession clustering problem

2016-03-10 Thread boulik
Hello. Here is: 2016-03-11 08:22:11,511 ERROR [http-bio-8080-exec-3 ] ROOT - Failed to update web session: null javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Failed to deserialize object with given class loader: null at

Re: Hibernate connection inspite of jdbc?

2016-03-10 Thread Ravi Puri
can U tell me what will be probable error in this part as it throws after returning listner succesfully? code: * cacheCfg.setCacheStoreSessionListenerFactories(new Factory() { @Override public CacheStoreSessionListener create() {

Re: Simple example of write-behind cache

2016-03-10 Thread vkulichenko
Kobe, No, this is a persistence store [1] implemented using Hibernate. When the cache is updated, it will use Hibernate session to update the database. In case of write-through consistency is guaranteed automatically by Ignite (if cache update fails, it will not update the database, and other way

Re: index and query org.apache.ignite.spark.IgniteRDD[String,org.apache.spark.sql.Row]

2016-03-10 Thread DmitryB
Spark SQL queries has the same problem -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/index-and-query-org-apache-ignite-spark-IgniteRDD-String-org-apache-spark-sql-Row-tp3343p3445.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Simple example of write-behind cache

2016-03-10 Thread Kobe
Val, Could you tell me how this works? Is this like a L2 cache for Hibernate? How is cache coherence maintained? Using Hibernate session listener alone? Thanx, /Kobe vkulichenko wrote > Hi Kobe, > > Take a look at this example: >

Re: index and query org.apache.ignite.spark.IgniteRDD[String,org.apache.spark.sql.Row]

2016-03-10 Thread Alexey Goncharuk
It looks like we are missing an option to tell IgniteRDD to work with binary objects. When an iterator is created, it tries to deserialize objects, and since you do not have a corresponding class, the exception occurs. I will create a ticket for this shortly. Despite this, you should still be

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

2016-03-10 Thread vkulichenko
Bhargav, Looks like you're still not subscribed to the mailing list. Can you please do this? Here is the short instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 bhargav wrote > Hi, > > Here is the link for the requested server node log > >

Re: websession clustering problem

2016-03-10 Thread vkulichenko
Hi Slavo, Can you provide the whole trace (looks like it's truncated)? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/websession-clustering-problem-tp3437p3441.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Simple example of write-behind cache

2016-03-10 Thread vkulichenko
Hi Kobe, Take a look at this example: https://github.com/apache/ignite/tree/master/examples/src/main/java-lgpl/org/apache/ignite/examples/datagrid/store/hibernate Sounds like that's exactly what you need. -Val -- View this message in context:

Re: Avoiding rebalance on process restart

2016-03-10 Thread Shaun Mcginnity
Hi Val, thanks for the reply. This option has avoided the automatic re-balance on failure. I can also see that the server reloads the cache contents when it restarts. Regards, Shaun On Thu, Mar 10, 2016 at 1:33 AM, vkulichenko wrote: > Hi Shaun, > > When the

Re: CacheStore handles persistence in client node for transactional cache

2016-03-10 Thread Vladimir Ozerov
Hi Kamil, By default TRANSACTIONAL cache invokes store from the node where transaction is started. If this is a client node, then store will be invoked from client. This is done on purpose to allow for transactional writes to store. ATOMIC cache, to the contrast, do not give any transactional

Re: Off Heap cache using lots of heap memory

2016-03-10 Thread Vladimir Ozerov
Hi Neil, Could you please attach the code reproducing the problem? Vladimir. On Wed, Mar 9, 2016 at 1:16 PM, Neil Wightman wrote: > Hi All, > > I have been trying out ignite for the past few weeks but I am hitting a > strange problem. I dont know if this problem

Re: C++ Client for SQL Queries

2016-03-10 Thread arthi
Thanks Igor. I used your master version of the header file and it worked! Thanks for all your help. Arthi -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/C-Client-for-SQL-Queries-tp3407p3433.html Sent from the Apache Ignite Users mailing list archive at

Re: @QuerySqlField for collections

2016-03-10 Thread Vladimir Ozerov
Hi Dmitry, I tried to reproduce you problem in Java using the following code, but without success: public class QueryListRunner { public static void main(String[] args) { IgniteConfiguration cfg = new IgniteConfiguration(); CacheConfiguration ccfg = new

Re: C++ Client for SQL Queries

2016-03-10 Thread Igor Sapego
Arthi, It is known issue [1]. It has been fixed already and this fix is going to be included to the next release. You can try using code from master brach or as a workaround you can try using no-throw method version instead i.e. QueryFieldsRow::GetNext(IgniteError& err). [1] -

Re: C++ Client for SQL Queries

2016-03-10 Thread arthi
Thanks Igor. It works! I am able to read the values from the cache using the C++ client. when I print the values from QueryFieldsCursor, I get a compilation error. This code follows your examples - Cache cache = grid.GetOrCreateCache("myCache"); SqlFieldsQuery qry(

Re: C++ Client for SQL Queries

2016-03-10 Thread Igor Sapego
Arthi, You can just put your additional libraries to $IGNITE_HOME/libs directory. Best Regards, Igor On Thu, Mar 10, 2016 at 7:56 AM, arthi wrote: > Thanks Igor. > > Well, I tried using a cache config in the XML to start my C++ client. but, > the factory

CacheStore handles persistence in client node for transactional cache

2016-03-10 Thread knowak
Hi, We configured partitioned, transactional cache with server and client nodes and CacheStore which handles write-through persistence. It seems that, however, in such model persistence logic (i.e. CacheStore.write() methods) can be invoked in client node for certain scenarios. After browsing