de modification.
>
> On Tue, 18 Aug, 2020, 2:47 am Evgenii Zhuravlev,
> wrote:
>
>> Hi,
>>
>> You can add cache configuration to the xml file with the *(for example,
>> cache-*) at the end. After this, caches with names that fit this
>> template(cache-1 fo
Thank you for the replay.
Now my existing code, don't have ignite templates.
To add templates, need to modify the code, but we don't have access for the
code modification.
On Tue, 18 Aug, 2020, 2:47 am Evgenii Zhuravlev,
wrote:
> Hi,
>
> You can add cache configuration to th
Hi,
You can add cache configuration to the xml file with the *(for example,
cache-*) at the end. After this, caches with names that fit this
template(cache-1 for template cache-*) will use it's cache configuration.
Evgenii
вс, 16 авг. 2020 г. в 07:03, C Ravikiran :
> As for the below
As for the below, I have to change in xml and java code also.
Is there there any other possibility, without changing the java code, and
changing only xml file, shall we achive cache configuration??
As we don't have the java code access, we have the access to the
configuration
xml file.
%20commands
.
On Sat., Aug. 15, 2020, 8:53 a.m. itsmeravikiran.c, <
itsmeravikira...@gmail.com> wrote:
> My cache ids are dynamic.
> Is it possible to add cache configuration in xml.
> I have checked, name property is mandatory. But i cannot add the name as
> it's dynamic name
My cache ids are dynamic.
Is it possible to add cache configuration in xml.
I have checked, name property is mandatory. But i cannot add the name as
it's dynamic name.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
and 2nd entries are clients and 3rd and 4th are server nodes.
>>> My client nodes has LRU near cache with size 10 and I am querying
>>> cache with 15 random data.
>>> But why there are heap entries on server nodes?
>>>
>>> wt., 24 mar 2020 o 08:
h size 10 and I am querying
>> cache with 15 random data.
>> But why there are heap entries on server nodes?
>>
>> wt., 24 mar 2020 o 08:40 Dominik Przybysz
>> napisał(a):
>>
>>> Hi,
>>> exactly I want to have near cache only on client no
;> I have two server nodes which keep data and I want to get data from them
>> via my client nodes.
>> I am also curious what had happened with heap on server nodes.
>>
>> pon., 23 mar 2020 o 23:13 Evgenii Zhuravlev
>> napisał(a):
>>
>>> Hi,
>>>
; pon., 23 mar 2020 o 23:13 Evgenii Zhuravlev
> napisał(a):
>
>> Hi,
>>
>> Near Cache configuration in xml creates near caches for all nodes,
>> including server nodes. As far as I understand, you want to have them on
>> client side only, right? If so, I'd
Zhuravlev
napisał(a):
> Hi,
>
> Near Cache configuration in xml creates near caches for all nodes,
> including server nodes. As far as I understand, you want to have them on
> client side only, right? If so, I'd recommend to create them dynamically:
> https://www.g
Hi,
Near Cache configuration in xml creates near caches for all nodes,
including server nodes. As far as I understand, you want to have them on
client side only, right? If so, I'd recommend to create them dynamically:
https://www.gridgain.com/docs/latest/developers-guide/near-cache#creating
-+
1st and 2nd entry is client node, 3rd and 4th is server node.
What is wrong with my near cache configuration?
Do I have to mirror all cache configuration on server node into client
nodes configuration? (for example, when I miss backup parameter I receiv
Hello!
2) Why? These classes will not be accessible by code running on Client.
Regards,
--
Ilya Kasnacheev
пн, 27 янв. 2020 г. в 23:43, Sabar Banks :
> Hello Ignite Community,
>
> My questions are:
>
> 1) Is it possible to only define cache configurations on the server side,
> via xml, and av
Hi!
1) You do not need to have cache configuration on client side, I do that
all the time.
2) Do not know
Mikael
Den 2020-01-27 kl. 21:42, skrev Sabar Banks:
Hello Ignite Community,
My questions are:
1) Is it possible to only define cache configurations on the server side,
via xml, and
Hello Ignite Community,
My questions are:
1) Is it possible to only define cache configurations on the server side,
via xml, and avoid defining caches on the client side?
2) Is it possible to only have data bean classes listed in a cache config,
to ONLY exist on the server side physically? I a
Thank you very much
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
No, it is not necessary. But you can supply additional configurations of
caches which will be started when client joins.
Regards,
--
Ilya Kasnacheev
ср, 27 февр. 2019 г. в 12:03, PBSLogitek :
> Hello
>
> I have a simple question. I have a server a node and some clients
> connecting
> t
Hello
I have a simple question. I have a server a node and some clients connecting
to it. In my server xml configuration i have defined all caches. Now my
question is do i have to define those caches in my client xml config to or
is it not necessary? Will i get an error when i try to access a cach
The SQL interface does not allow you to configure details of the cache
except via templates. The use case is I want to start with the cluster
specific defaults for a cache, and add some others.
I can create a empty real cache that has the defaults, and use its
configuration in the CacheConfigura
Hello!
Why don't you just use CREATE TABLE for that? I doubt there will be any
significant overhead even if you never use any SQL and only use Cache API
after that.
Regards,
--
Ilya Kasnacheev
вт, 28 авг. 2018 г. в 17:37, Dave Harvey :
> I did a suggested edit adding the Spring configuration
I did a suggested edit adding the Spring configuration of templates.The
rest of the current semantics seem a bit odd, so I was somewhat at a loss
as to what to write.
The wildcard approach means that I have to know the structure of the cache
name a priori. Seems like there should be a Java A
Hello!
Unfortunately, cache templates are not documented that good. AFAIK they
were mostly implemented to be able to reference to complex cache
configurations with CREATE TABLE.
As far as my understanding goes, caches from cacheConfigurations are
actually started when grid starts.
1) I think tha
I found what I've read in this area confusing, and here is my current
understanding.
When creating an IgniteConfiguration in Java or XML, I can specify the
property cacheConfiguration, which is an array of CacheConfigurations.
This causes Ignite to preserve these configurations, but this will not
Ignite internally guarantees that write through to the 3rd party cache
store will be consistent with the update of the cache.
Evgenii
2018-07-09 17:50 GMT+03:00 Prasad Bhalerao :
> When you have multiple data sources (cache and oracle in this case) which
> should be updated in single transaction
When you have multiple data sources (cache and oracle in this case) which
should be updated in single transaction we use JTA. But with ignite
transaction and ignite write through approach I don't have to use JTA.
To keep the cache and oracle consistent one needs transaction. In this
case one updat
No, you're not correct, each insert/update will be consistent between cache
and DB, transactions are not about consistency between cache and oracle
database here, it's about more than one operation, as in an example I've
shared in my previous message.
Evgenii
2018-07-09 17:24 GMT+03:00 Prasad Bha
Thank you for the clarification.
Ignite does not support transactions with jdbc updates. So if I use
delete/update SQL to delete/update the multiple cache entries, ignite will
not provide strong consistency between cache and oracle database.
Am I correct?
On Mon, Jul 9, 2018 at 7:43 PM Evgenii Zh
1. As this doc says: https://apacheignite.readme.io/docs/3rd-party-store:
Ignite writes through results of its SQL INSERT, UPDATE and MERGE queries.
2. Transaction in Ignite means absolutely the same as in another systems.
If you want two or more changes to be in one transaction(i.e., classic
examp
Resending my last mail ...
I understand that FULL_SYNC is required to keep the consistency between
primary data node and backup data node and not between the cache and 3rd
party data.
Sorry for asking the incorrect question.
1) Does ignite supports write through updates to 3rd party store when us
Hi,
1. Cache write synchronization mode is not about 3rd party store, it's
about waiting for write replies from other nodes. But Ignite with enabled 3rd
party store guarantees consistency itself.
2. Ignite creates implicit transactions for atomic updates to guarantee
consistency between nodes. If
I understand that FULL_SYNC is required to keep the consistency between
primary data node and backup data node and not between the cache and 3rd
party data.
Sorry for asking the incorrect question.
1) Does ignite supports write through updates to 3rd party store when using
update or delete sql?
2
Hi,
I am using FULL_SYNC cache write synchronization mode.
1) Does FULL_SYNC mode guarantees 100% consistency between ignite in memory
cache and 3rd party data store (oracle in my case)?
2) Does FULL_SYNC mode requires to do the cache updates in ignite
transaction?( I am using write through appro
Oh, I see now that we are talking about Factory
:)
Yes, it looks like a usability issue or even a bug. The implementation
should inject dependencies into that factory in the same way it does for
CacheStoreFactory.
As a workaround, you can try the following:
private CacheConfiguration ipContainerIP
> I tried to debug the ignite code, GridResourceProcessor.inject is not
> being executed for injecting resources into CacheStoreSessionListener. It
> is being called for Cachestores.
>
> Can you please advise?
>
> Thanks,
> Prasad
>
> On Thu, Jul 5, 2018 at 8:14 PM Prasad Bhalerao <
> prasadbhalera
I tried to debug the ignite code, GridResourceProcessor.inject is not being
executed for injecting resources into CacheStoreSessionListenerFactories.
It is being called for CachestoreFactories.
Can you please advise?
Thanks,
Prasad
On Thu, Jul 5, 2018 at 8:14 PM Prasad Bhalerao
wrote:
> I had
I had used SpringApplicationContextResource annotation. But it did not
inject the application context in it. So I decided to use spring managed
bean and it worked but now it is creating the problem which is described in
this mail chain.
On Thu, Jul 5, 2018 at 8:11 PM Prasad Bhalerao
wrote:
> I
I had used SpringApplicationContextResource annotation. But it did not
inject the application context in it. So I decided to use spring managed
bean and it worked.
Thanks,
Prasad
On Thu, Jul 5, 2018 at 7:49 PM Вячеслав Коптилин
wrote:
> It seems that you need to use @
>
> SpringApplicationCont
It seems that you need to use @
SpringApplicationContextResource
instead of @Autowired.
Could you please check that?
Thanks.
чт, 5 июл. 2018 г. в 17:01, Prasad Bhalerao :
>
>
> import java.io.Serializable;
> import javax.cache.configuration.Factory;
> import javax.sql.DataSource;
> import org.
import java.io.Serializable;
import javax.cache.configuration.Factory;
import javax.sql.DataSource;
import org.apache.ignite.IgniteException;
import org.apache.ignite.cache.store.CacheStoreSessionListener;
import org.apache.ignite.cache.store.jdbc.CacheJdbcStoreSessionListener;
import org.springfra
Well, the exception is thrown by your class:
org.apache.ignite.IgniteException: Spring application context resource is
not injected.
at
*com.qualys.agms.grid.cache.loader.factory.CacheStoreSessionListenerFactory*.create(CacheStoreSessionListenerFactory.java:30)
at
com.qualys.agms.grid.cache.loade
Hi,
I am using Ignite 2.4 version. Please find attached the log files. Log file
agms-web is a client node log and agms-core is server node log.
Ignite configuration on client node is as follows. When I try to get the
cache contents on client node after data push operation, my request hangs
on ign
Hello Prasad,
I cannot reproduce the behavior that you described.
Please share the code that the community can use in order to reproduce the
issue.
It would be nice to have log files from both nodes (client and server).
One more thing. Could you please share the version of Apache Ignite that you
Hi,
Try advice to call ignite.getOrCreateCache("cacheName");, got a feeling that
you will get an empty cache there which would mean that this cache is not
created yet or is failing to start. In this case please attach startup logs
for server/client nodes setup.
Regards.
--
Sent from: http://a
question is.
Is it necessary to provide all cache configuration on client node as well?
If yes why?
Thanks,
Prasad
On Thu, Jul 5, 2018 at 5:23 PM Maxim Malygin
wrote:
> Please show stack trace of your NPE.
>
> Regards,
> Maxim
>
> чт, 5 июл. 2018 г. в 14:48, Prasad Bhalerao
s present on ignite server node. But when I access
>>> the same cache from client node I get NullPointerException when I execute
>>> following code on client node.
>>>
>>> ignite.cache(getCacheName())
>>>
>>> Is it necessary to provide all cache configuration on client node as
>>> well?
>>> If yes why?
>>>
>>> Thanks,
>>> Prasad
>>>
>>
>>
tarted in client mode does not
>> have any cache configurations.
>>
>> Now case is cache is present on ignite server node. But when I access the
>> same cache from client node I get NullPointerException when I execute
>> following code on client node.
>>
>> ign
rted in client mode does not
> have any cache configurations.
>
> Now case is cache is present on ignite server node. But when I access the
> same cache from client node I get NullPointerException when I execute
> following code on client node.
>
> ignite.cache(getCach
NullPointerException when I execute
following code on client node.
ignite.cache(getCacheName())
Is it necessary to provide all cache configuration on client node as well?
If yes why?
Thanks,
Prasad
Hello,
> Do I need to configure something else for off heap eviction?
If you are using Ignite Native Persistence, you don't need to configure
page-based eviction.
In that case, it will be automatically enabled. Please take a look at this
page for the details:
https://apacheignite.readme.io/docs/e
Do I need to configure something else for off heap eviction?
I have on heap enabled and set eviction policy(LRU). Max size of 1MB also
provided. I have 1.5million data, so obviously it some entries loaded in the
start should be evicted. Still when I try to get those entries, I get
performance equi
> I guess durable memory is pure RAM based and native persistence is
combination of both RAM and disk.
Durable memory is a memory architecture that allows processing and storing
data both in memory and on disk. In other words, Ignite native persistence
is a feature(add-on) provided by Durable memor
Thanks, every thing other than native vs durable is now clear for me.
I guess durable memory is pure RAM based and native persistence is
combination of both RAM and disk.
How to manipulate durable memory? Can I configure it?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
> 1. I have set setOnheapCacheEnabled(true) for every cache.
> This means they will go into java heap right?
As of AI 2.x Java heap is no longer treated as a data storage
and might be used as an extra caching layer for entries you have in the
off-heap.
> 2. I don't clearly understand the dif
Hi,
1. I have set setOnheapCacheEnabled(true) for every cache. This means they
will go into java heap right?
2. Is it possible for me to take control of this durable memory? What should
essentially be kept there? How to do that? I don't clearly understand the
difference between durable memory and
Hello,
As of Apache Ignite 2.x, all data are stored into off-heap memory [1].
On-heap memory is used only for temporary operations, buffers etc.
> Also, I have my own cache store implementations. I hope this is only used
> for read through and
> write through from and to database and not for load
Hi,
I have multiple on heap caches attached to a data region of maximum 1GB size
durable memory. I have 512MB heap memory specified also.
Is it possible for me to set the size of this cache to take maximum of 100MB
and store the remaining in durable memory? Otherwise, won't it be using the
entire
@ignite.apache.org
Subject: IgniteCheckedException: Failed to validate cache configuration.
Cachestore 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 there any solutions?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
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.Serializab
Thanks Ilya it answers my question
On 29 Jan 2018 3:34 p.m., "ilya.kasnacheev"
wrote:
> Hello Rajesh!
>
> In Ignite, cache (and SQL table) maps not to one object but to two - key
> and
> value.
>
> Keys are unique per cache per cluster. They act as primary key in SQL and
> as, well, keys in cach
Hello Rajesh!
In Ignite, cache (and SQL table) maps not to one object but to two - key and
value.
Keys are unique per cache per cluster. They act as primary key in SQL and
as, well, keys in cache API.
So yes, you need to specify key type (or compound object) too.
Regards,
Ilya.
--
Sent from:
Hi All,
I have a requirement to define a cache class, for which its instance
qualifies only for value.
public class EntryIndexedAttributes
{
@QuerySqlField( orderedGroups = { @QuerySqlField.Group(
name = "generic_attr_idx", order = 0) ,
@QuerySqlField.Group(
name = "gener
I believe i had the same issue, i have posted a test and my finding to the
user group. Which can be found here.
http://apache-ignite-users.70518.x6.nabble.com/Near-Cache-Topoolgy-change-causes-NearCache-to-always-miss-td17539.html
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
To answer your question, using Visor, one can see cache misses increase upon
the scenario described. Furthermore, measure cache.get() calls increase
from sub millisecond to 20 to 30 miillis.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello,
It looks like you trying to start node which has an inconsistent
configuration for atomic types.
Please check that all nodes in the cluster (clients and servers) have the
identical configuration [1].
something like the following:
[1] https://ap
Was just hit with this error causing my whole ignite cluster to fail to
start:
org.apache.ignite.IgniteCheckedException: Affinity key backups mismatch (fix
affinity key backups in cache configuration or set
-DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property)
[cacheName=ignite
Hello,
Could you say how you determine that client node loads data from remote
node bypasses near cache?
I'm not able reproduce this behaviour locally, could you share a simple
maven project that reproduces this behaviour?
On Tue, Oct 17, 2017 at 12:54 AM, torjt wrote:
> Hello All,
>
> We are h
+ user list
> On Oct 20, 2017, at 11:00 PM, Denis Magda wrote:
>
> Ignite caching experts please chime in.
>
>> Begin forwarded message:
>>
>> From: torjt
>> Subject: Client Near Cache Configuration Lost after Cluster Node Removed
>> Date: Octo
Hello All,
We are having an issue with Ignite client near caches being "lost" upon a
cluster node being removed from the Ignite cluster. Furthermore, using
version 2.1.0, we are seeing this issue when another client joins the
topology. I built Ignite from GIT today, 10/16/17, with the latest cha
Rick,
writeThrough property enables cache store integration overall, while
writeBehindEnabled property controls whether store updates are async or not.
So this is correct behavior.
As for transactions, write-behind store updates are always non
transactional. I.e. you will have a transaction in ca
Hi,
I am using Ignite 2.0.0 with a cache configurations shown below. First, I
noticed that writeAll() or any write() was not called on my cache store when
writeBehindEnabled=true but writeThrough=false. Seems like if
writeBehindEnabled set to true, it should override writeThrough, but anyway,
I
be
possible when we have full DDL support.
[1] https://apacheignite.readme.io/docs/binary-marshaller
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Dynamically-update-the-Cache-Configuration-without-restsrting-client-and-serve-tp14303p14427.html
Sent from
configuration can be changed in
runtime?
It will be very helpful if you can point me to some documentation which lists
all the parameters for cache configuration in a single place.
Regards,
Priya
-Original Message-
From: vkulichenko [mailto:valentin.kuliche...@gmail.com]
Sent: 06 July 2017 01
Hi Priya,
Cache configuration can't be changed in runtime in any of the versions. What
properties are you looking to change exactly?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Dynamically-update-the-Cache-Configuration-without-restsrting-clien
updated/cannot be updated
listed in any document? Any reference to the link will help a lot.
Thanks,
Priya
From: Nikolai Tikhonov [mailto:ntikho...@apache.org]
Sent: 04 July 2017 22:58
To: user@ignite.apache.org
Subject: Re: Dynamically update the Cache Configuration without restsrting
client and
th my web application. I am
> using Java Configuration using IgniteConfiguration and CacheConfiguation
> beans to configure the Caches and my Ignite
> Configuration.
>
> I want to the update the Apache Ignite Cache Configuration without
> restarting the web application.
>
>
Hi,
I am using Apache Ignite in client mode true with my web application. I am
using Java Configuration using IgniteConfiguration and CacheConfiguation
beans to configure the Caches and my Ignite
Configuration.
I want to the update the Apache Ignite Cache Configuration without
restarting the
Hi,
Atomic configuration must be consistent on all nodes. As for general cache
configuration, you also must be consistent on all nodes if it's provided on
startup. However, it's ok if there is a configuration for a particular cache
only on client - it will distributed during cache st
lost. Is there a rule of thumb to follow?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Affinity-key-backups-mismatch-fix-affinity-key-backups-in-cache-configuration-or-set-DIGNITE-SKIP-COy-tp10305p10307.html
Sent from the Apache Ignite Users mailing list archive
and Ignite server should have? And what would be the
consequences of not keeping them in sync?
As my Ignite server has extensive configuration for each of the cache used
with cachestore, eviction/expiry policies, etc. While my Ignite client
doesn't have anything related to the cache configur
y key backups mismatch (fix
affinity key backups in
cache configuration or set
-DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true system property)
[cacheName=ignite-atomics-sys-cache, localAffinityKeyBackups=0,
remoteAffinityKeyBacku
ps=1, rmtNodeId=ffaee6a8-19b2-4168-8d9d-dafd4f9a1316]
I su
Hi, Shawn Du!
No, it is not possible.
You need to destroy cache a re-create with new configuration.
On Mon, Dec 19, 2016 at 9:33 AM, Shawn Du wrote:
> Hi,
>
>
>
> It is possible to alter cache configuration after cache created and
> running?
>
>
>
> Thanks
>
Hi,
It is possible to alter cache configuration after cache created and running?
Thanks
Shawn
Hi,
Index field name must be unique across both a key and a value. Check the
implementation of your key and value and make sure that there is no duplicates.
—
Denis
> On Jul 12, 2016, at 5:01 AM, deleerhai <185961...@qq.com> wrote:
>
> Hi,
> Create cache configuration
Hi deleerhai
Could you show source and class hierarchy for ContractInfo.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Create-cache-configuration-error-tp6218p6226.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
Create cache configuration error.
<http://apache-ignite-users.70518.x6.nabble.com/file/n6218/1.png>
<http://apache-ignite-users.70518.x6.nabble.com/file/n6218/2.png>
七月 12, 2016 10:13:19 上午 org.apache.catalina.core.ApplicationContext log
严重: StandardWrapp
of
> > each server. Some exceptions seen during server close.
> > 8) getOrCreate near caches again on client nodes.
> > 9) Try putting objects again. Exception occurred.
> >
> > Regards,
> > Vinay
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3310.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
ry putting objects again. Exception occurred.
>
> Regards,
> Vinay
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3310.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3307.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Vladimir,
Sure. I am up for any assistance to make Ignite better.
I shared server configs and stacktraces in previous communications. I will
try my best to replicate this issue again. If i could find exact steps
then i will try to write a test case for simplification.
It may take some time f
tart encapsulated Ignite instance in my custom cache
> manager. I landed in a issue there which i will share in a separate
> thread.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-
ch ,out of many other
tasks, can also restart encapsulated Ignite instance in my custom cache
manager. I landed in a issue there which i will share in a separate thread.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-se
//apache-ignite-users.70518.x6.nabble.com/file/n3085/default-config.xml
> >
>
> visor_ignite_stack_trace_masked.txt
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/n3085/visor_ignite_stack_trace_masked.txt
> >
>
> Regards,
> Vinay Sharma
>
>
>
> --
> View this message in context:
://apache-ignite-users.70518.x6.nabble.com/file/n3085/visor_ignite_stack_trace_masked.txt>
Regards,
Vinay Sharma
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3085.html
S
case?
>>
>> -Val
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-node
server
> nodes in the topology. Is this the case?
>
> -Val
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarte
successful ones.
Most likely you were getting these exceptions when there were no server
nodes in the topology. Is this the case?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception
.ignite.IgniteException: Failed to
deserialize object with given class loader: WebappClassLoader
Regards,
Vinay Sharma
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064.html
Sent from th
Ok,
Thank you!
Romain
Le mar. 26 janv. 2016 à 11:28, Alexey Goncharuk
a écrit :
> Hi Romain,
>
> No, if you set storeKeepBinary(true), then values will be passed to a
> store in binary format regardless of the withKeepBinary() flag on cache API.
>
>
1 - 100 of 102 matches
Mail list logo