[
https://issues.apache.org/jira/browse/IGNITE-10572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719075#comment-16719075
]
Ignite TC Bot commented on IGNITE-10572:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2522425]]
* HibernateL2CacheTransactionalSelfTest.testCollectionCache (last started)
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2522424]]
* HibernateL2CacheTransactionalUseSyncSelfTest.testRegionClear (last started)
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2522508&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC TX: Possible race on invokeAll operations
> ----------------------------------------------
>
> Key: IGNITE-10572
> URL: https://issues.apache.org/jira/browse/IGNITE-10572
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Igor Seliverstov
> Assignee: Andrew Mashenkov
> Priority: Major
> Fix For: 2.8
>
>
> seeĀ {{GridNearTxEnlistFuture#checkResponse}} method.
> 1) race on result creation - two threads may see {{this.res == null}} and
> just set their values, result is partially lost
> 2) race on success flag set - just set false flag may be overwritten by
> concurrent successful response checking operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)