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.

Solutions on the web126

  • 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
    , 9 months 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.
  • 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.
  • Stack trace

    • 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) at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toObject(AbstractSerializationService.java:165) at com.hazelcast.nio.tcp.TcpIpConnectionManager.handle(TcpIpConnectionManager.java:233) at com.hazelcast.spi.impl.NodeEngineImpl$ConnectionManagerPacketHandler.handle(NodeEngineImpl.java:124) at com.hazelcast.spi.impl.packetdispatcher.impl.PacketDispatcherImpl.dispatch(PacketDispatcherImpl.java:63) at com.hazelcast.nio.tcp.MemberReadHandler.handlePacket(MemberReadHandler.java:75) at com.hazelcast.nio.tcp.MemberReadHandler.onRead(MemberReadHandler.java:58) at com.hazelcast.nio.tcp.nonblocking.NonBlockingSocketReader.handle(NonBlockingSocketReader.java:178) at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.handleSelectionKey(NonBlockingIOThread.java:271) at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.handleSelectionKeys(NonBlockingIOThread.java:256) at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.runSelectLoop(NonBlockingIOThread.java:206) at com.hazelcast.nio.tcp.nonblocking.NonBlockingIOThread.run(NonBlockingIOThread.java:163)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    2 times, 11 months ago
    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 11 months ago
    3 more bugmates