com.hazelcast.nio.serialization.HazelcastSerializationException: There is no suitable de-serializer for type 65536. This exception is likely to be caused by differences in the serialization configuration between members or between clients and members.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by Martin Lichtin, 1 year ago
There is no suitable de-serializer for type 65536. This exception is likely to be caused by differences in the serialization configuration between members or between clients and members.
via GitHub by pysjp
, 1 year ago
There is no suitable de-serializer for type 65536. This exception is likely to be caused by differences in the serialization configuration between members or between clients and members.
via Stack Overflow by user8690484
, 1 month ago
There is no suitable de-serializer for type 16843028. This exception is likely to be caused by differences in the serialization configuration betw een members or between clients and members.
via Google Groups by Unknown author, 4 months ago
There is no suitable de-serializer for type 16843028. This exception is likely to be caused by differences in the serialization configuration betw een members or
via Stack Overflow by I. Domshchikov
, 1 year ago
There is no suitable de-serializer for type 2. This exception is likely to be caused by differences in the serialization configuration between members or between clients and members.
via GitHub by hasancelik
, 1 year ago
There is no suitable de-serializer for type -201. This exception is likely to be caused by differences in the serialization configuration between members or between clients and members.
com.hazelcast.nio.serialization.HazelcastSerializationException: There is  no suitable de-serializer for type 65536. This exception is likely to be  caused by differences in the serialization configuration between members or  between clients and members.	at com.hazelcast.internal.serialization.impl.AbstractSerializationService.newHazelcastSerializationException(AbstractSerializationService.java:183)[157:com.hazelcast:3.6.4]	at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toObject(AbstractSerializationService.java:165)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.TcpIpConnectionManager.handle(TcpIpConnectionManager.java:233)[157:com.hazelcast:3.6.4]	at com.hazelcast.spi.impl.NodeEngineImpl$ConnectionManagerPacketHandler.handle(NodeEngineImpl.java:124)[157:com.hazelcast:3.6.4]	at com.hazelcast.spi.impl.packetdispatcher.impl.PacketDispatcherImpl.dispatch(PacketDispatcherImpl.java:63)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.MemberReadHandler.handlePacket(MemberReadHandler.java:75)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.MemberReadHandler.onRead(MemberReadHandler.java:58)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.nonblocking.NonBlockingSocketReader.handle(NonBlockingSocketReader.java:178)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.handleSelectionKey(NonBlockingIOThread.java:329)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.handleSelectionKeys(NonBlockingIOThread.java:314)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.selectLoop(NonBlockingIOThread.java:234)[157:com.hazelcast:3.6.4]	at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.run(NonBlockingIOThread.java:187)[157:com.hazelcast:3.6.4]