[
https://issues.apache.org/jira/browse/IGNITE-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379993#comment-16379993
]
Alexey Kuznetsov commented on IGNITE-6083:
------------------------------------------
[~agoncharuk] Hi!
I added multi-threaded test you described above.
Also new tests for pessimitic mode were added, and they revealed bug in
pessimitic scenarios.
The bug is fixed, and you can review the whole ticket once more.
To sum up, the following tests I included in PR :
testTxInvokeSequentialOptimisticConflict - Tests that optimistic conflict
occures when value is changed outside the serizlizable transaction.
testTxInvokeSequentialCallOnNearNode - Tests that sequential invoke call works
correct. In this test the value is fetched from remote node. In pessimitic
mode, the bug occured in this test.
testTxInvokeSequentialCallOnPrimaryNode - Tests that sequential invoke call
works correct. In this test the value is located on local node, original test.
Also, run tests on teamcity. You can review it :
[TC
run|https://ci.ignite.apache.org/viewLog.html?buildId=1113310&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
[Upsource
review|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-395?filePath=/modules/core/src/test/java/org/apache/ignite/testsuites/IgniteCacheTestSuite.java]
[PR|https://github.com/apache/ignite/pull/2975]
> Null value have appear in the entry processor, but the entry is existing
> ------------------------------------------------------------------------
>
> Key: IGNITE-6083
> URL: https://issues.apache.org/jira/browse/IGNITE-6083
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.1
> Reporter: Vladislav Pyatkov
> Assignee: Alexey Kuznetsov
> Priority: Major
> Attachments: EntryProcessorInOptimisticTxTest.java
>
>
> In one thread load some data in a cache, after that I have execute
> OPTIMISTIC, SERIALIZABLE transaction with two {{IgniteCache.invoke()}}
> methods.
> The value had been corrected at first {{EntryProcessor}}, but it is NULL at
> second.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
