ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-4760) Hibernate L2 cache stores value in wrong cache
Date Thu, 06 Apr 2017 10:54:42 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Semen Boikov updated IGNITE-4760:
    Fix Version/s:     (was: 2.0)

> Hibernate L2 cache stores value in wrong cache
> ----------------------------------------------
>                 Key: IGNITE-4760
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4760
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: Hibernate L2 cache
>            Reporter: Semen Boikov
>            Assignee: Vadim Opolski
>             Fix For: 2.1
> Issue is reported here:
> http://apache-ignite-developers.2346864.n4.nabble.com/issue-with-Hibernate-2L-cache-region-factory-ignite-1-8-td14912.html
> First it is necessary add JUnit test reproducing issue (see existing tests in IgniteHibernateTestSuite).
> Currently Hibernate access strategies track updates using thread locals, and it looks
like updates for different caches can be mixed. I think per-cache thread local can fix issue
for HibernateNonStrictAccessStrategy, but per-cache thread local can not be used for HibernateReadWriteAccessStrategy,
since it is assumed that all updates should be part of the same cross-cache ignite transaction.
> So possible fix:
> - use per-cache thread local for HibernateNonStrictAccessStrategy (or somehow track target
cache in HibernateNonStrictAccessStrategy)
> - use single thread local for HibernateReadWriteAccessStrategy

This message was sent by Atlassian JIRA

View raw message