Hi,
It looks like the application has Geronimo JCache spec [1] on the classpath.
It's fully compatible with the original JCache spec on API level, but there
are different serial versions on some of serializable classes. Please make
sure that the same version is used on everywhere in the cluster.
As I know JdkMarshaller used for serialization of internal ignite objects,
such as continuous query, distributed services etc., not for cache entries.
In your case the exception occured during deserialization of object
javax.cache.configuration.MutableConfiguration.
This class is from cache-api
I will definitely let you know if I can reproduce it, but just for my own
understanding, as you saw in the sample, I was just storing strings, so what
could have caused the serialization exception? Just want to avoid misusing the
API.
On Tuesday, October 11, 2016 8:14 AM, Sergej Sidorov
Hi,
For internal activities ignite use only work directory.
Let me know if the issue is reproduced again.
-Sergej
--
View this message in context:
Hi M Singh!
I can't reproduce this. Could you provide your eclipse project?
-Sergej
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Iginte-Exception-Failed-to-unmarshal-discovery-data-for-component-1-on-starting-server-from-console-E-tp8160p8173.html
Sent from
