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.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web127

  • 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)[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]

    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