There is no suitable de-serializer for type

[Hrishikesh Joshi]

While doing load using MapStore I am getting 

com.hazelcast.nio.serialization.HazelcastSerializationException: There is no suitable de-serializer for type 67 for a perticular object when its trying to readObject from serializer. And I am getting this exception with different type no e.g.

There is no suitable de-serializer for type 60,

There is no suitable de-serializer for type 76,

There is no suitable de-serializer for type 131

There is no suitable de-serializer for type 142

etc. Not able to find a root cause of this. could someone please help on this?

[Peter Veentjer]

Could it be that you are mixing different versions of HZ?

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at http://groups.google.com/group/hazelcast.
To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/66257e23-813e-4af0-b823-42ff8e2e33f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter Veentjer]

This can also easily happen by accident if multiple jars of different version are found on the classpath. Then it becomes a crap-shoot which version is going to win.

[Hrishikesh Joshi]

You mean different versions of Hazlecast are on classpath? Well no I am using 3.5.2 version only.

[Peter Veentjer]

Could you print 'java.class.path' from the system properties and look for Hazelcast?



And can you verify that all members + clients work with 3.5.x (on patch level we are compatible; so 3.5.1 will work with 3.5.4)


To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/3d293bad-a838-4be7-9125-fa6544508ef9%40googlegroups.com.

[Hrishikesh Joshi]

There is only one hazelcast-all jar in classpath of version 3.5.2.

[Peter Veentjer]

Hmmm.. I'm a bit flabbergasted.

How easy is it to reproduce? Can you create a unit tests/main that can reproduce it?

To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/10dd8298-1a39-4907-b77a-bb02cd8fd8e6%40googlegroups.com.

[dsukho...@gmail.com]

Are you sure you registered serialization factory properly?

[Hrishikesh Joshi]

I have registered serializer implementing StreamSerializer as

<hz:serialization>

<hz:serializers>

<hz:serializer type-class="CacheObject"

class-name="SerializerClass" />

Its working for other objects for this perticular object, it is a composite object where 

lets say CacheObject has a field field1 of type CacheObject1 which is also being stored in a different map and has its own serializer. Serializer failing when it is doing readObject for this CacheObject1 field.

[Peter Veentjer]

Can you create a unit test that reproduces the problem? Then it will be a lot easier for us to find the cause and provide a solution.

--

You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at http://groups.google.com/group/hazelcast.

To view this discussion on the web visit https://groups.google.com/d/msgid/hazelcast/1232971b-a65c-42e4-8d8a-5d5639cffc61%40googlegroups.com.