Mailing-List: contact issues-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Date: Wed, 25 Mar 2015 17:50:54 +0000 (UTC)
From: "Artem Shutak (JIRA)" <jira@apache.org>
To: issues@ignite.incubator.apache.org
Message-ID: <JIRA.12785619.1427305835000.26062.1427305854918@Atlassian.JIRA>
In-Reply-To: <JIRA.12785619.1427305835000@Atlassian.JIRA>
References: <JIRA.12785619.1427305835000@Atlassian.JIRA>
 <JIRA.12785619.1427305835837@arcas>
Subject: [jira] [Created] (IGNITE-592) [Test] Null can be erroneously passed
 to filter in optimistic transaction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Artem Shutak created IGNITE-592:
-----------------------------------

             Summary: [Test] Null can be erroneously passed to filter in optimistic transaction
                 Key: IGNITE-592
                 URL: https://issues.apache.org/jira/browse/IGNITE-592
             Project: Ignite
          Issue Type: Bug
            Reporter: Artem Shutak
            Assignee: Yakov Zhdanov
             Fix For: sprint-3


For optimsitic transaction filter is applied in GridCacheTxLocalAdapter.enlistWrite, and there are two issues:
- when put is started from backup node we pass to filter detached entry without value, so that GridCacheEntry.peek returns null even if we have value locally
- when offheap is enabled then entry is unswapped before it is passed to filter, but there is a race so that another thread can swap it again before filter is applied (GridCacheOffHeapMultiThreadedUpdateSelfTest.testPutWithFilterTx)

see GG-8118


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)