[
https://issues.apache.org/jira/browse/IGNITE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976847#comment-15976847
]
Semen Boikov commented on IGNITE-3429:
--------------------------------------
Implemented multi-jvm test which fails with BinaryMarshaller in 1.9 and pass
with 2.0, so I can consider workaround with BinaryIdentityResolvers is not
needed in current implementation.
> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -----------------------------------------------------------------------------
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
> Issue Type: Sub-task
> Components: cache, Hibernate L2 cache
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Assignee: Semen Boikov
> Priority: Blocker
> Fix For: 2.0
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries
> in the Hibernate L2 cache. This class contains {{type}} field and custom
> {{equals}} logic where the type is used as a helper and does not participate
> in comparison. Instances of the same type are producing different hash codes
> in different JVMs, which actually breaks comparison when binary format is
> used, where byte arrays are compared.
> The issue is described in more detail here:
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
