You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Roman Guseinov (JIRA)" <ji...@apache.org> on 2018/06/19 03:05:00 UTC

[jira] [Created] (IGNITE-8824) .NET: Invalid header on deserialization

Roman Guseinov created IGNITE-8824:
--------------------------------------

             Summary: .NET: Invalid header on deserialization
                 Key: IGNITE-8824
                 URL: https://issues.apache.org/jira/browse/IGNITE-8824
             Project: Ignite
          Issue Type: Bug
          Components: binary, platforms
    Affects Versions: 2.5
            Reporter: Roman Guseinov
         Attachments: InteropreabilityTest.cs, ServerNode.java

The issue happens when we save an object with java.util.Date field in Java and retrieves that one on .NET side (DateTime). According to the docs these types should be compatible [1].
{code:java}
Apache.Ignite.Core.Binary.BinaryObjectException: 'Invalid header on deserialization [pos=34, hdr=11]'
{code}
The workaround is java.sql.Timestamp instead of Date type.

Java and C# code examples to reproduce the issue are attached: [^ServerNode.java][^InteropreabilityTest.cs]

[1] [https://apacheignite-net.readme.io/v2.1/docs/platform-interoperability#section-type-compatibility]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)