[
https://issues.apache.org/jira/browse/IGNITE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673619#comment-15673619
]
Fred commented on IGNITE-3429:
------------------------------
That hurts pushing it to 2.0, I havent found a solid way of getting Hibernate
L2 cache working:
http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities
http://stackoverflow.com/questions/40140645/apache-ignite-hibernate-sessionfactory-serialization-issue
https://issues.apache.org/jira/browse/IGNITE-1794
http://apacheignite.gridgain.org/docs/binary-marshaller
> 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: Bug
> Components: cache
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Priority: Critical
> 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.4#6332)
