[
https://issues.apache.org/jira/browse/IGNITE-8824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516604#comment-16516604
]
Roman Guseinov commented on IGNITE-8824:
----------------------------------------
The issue is reproducible on the master branch.
> .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
> Priority: Major
> Labels: dot_net
> 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)
