Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BC5E7200C6A for ; Wed, 19 Apr 2017 13:05:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BAFBF160B86; Wed, 19 Apr 2017 11:05:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0E6E1160B94 for ; Wed, 19 Apr 2017 13:05:44 +0200 (CEST) Received: (qmail 17654 invoked by uid 500); 19 Apr 2017 11:05:43 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 17548 invoked by uid 99); 19 Apr 2017 11:05:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Apr 2017 11:05:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3CAFF189FCC for ; Wed, 19 Apr 2017 11:05:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -98.688 X-Spam-Level: X-Spam-Status: No, score=-98.688 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id EdeBrCeXJh7q for ; Wed, 19 Apr 2017 11:05:42 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 5A9705FCAE for ; Wed, 19 Apr 2017 11:05:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DAC3DE07E1 for ; Wed, 19 Apr 2017 11:05:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8E13921B47 for ; Wed, 19 Apr 2017 11:05:41 +0000 (UTC) Date: Wed, 19 Apr 2017 11:05:41 +0000 (UTC) From: "Semen Boikov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-4760) Hibernate L2 cache stores value in wrong cache MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 19 Apr 2017 11:05:45 -0000 [ https://issues.apache.org/jira/browse/IGNITE-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974450#comment-15974450 ] Semen Boikov commented on IGNITE-4760: -------------------------------------- Also I found that this issue is reason of https://issues.apache.org/jira/browse/IGNITE-1084. Vadim, please check that HibernateL2CacheSelfTest#testNaturalIdCache() does not fail after your changes. Thanks! > 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 (v6.3.15#6346)