[
https://issues.apache.org/jira/browse/IGNITE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Shutak updated IGNITE-582:
--------------------------------
Description:
Ticket is related to this issue
http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions.
I added more simple test to the GridCacheTxMultiThreadedAbstractTest.
Original test is also attached to the ticket. Sometimes commit fails with
GridCacheTxOptimisticException, but two threads still can commit duplicated
values so that increment is lost.
see GG-8063
Next test(s) should be unmuted on TC: testOptimisticSerializableConsistency
was:
Ticket is related to this issue
http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions.
I added more simple test to the GridCacheTxMultiThreadedAbstractTest.
Original test is also attached to the ticket. Sometimes commit fails with
GridCacheTxOptimisticException, but two threads still can commit duplicated
values so that increment is lost.
see GG-8063
testOptimisticSerializableConsistency have to be unmuted.
> [Test] Unexpected behavior for OPTIMISTIC SERIALIZABLE transaction
> ------------------------------------------------------------------
>
> Key: IGNITE-582
> URL: https://issues.apache.org/jira/browse/IGNITE-582
> Project: Ignite
> Issue Type: Bug
> Reporter: Artem Shutak
> Assignee: Yakov Zhdanov
> Labels: failedtest
>
> Ticket is related to this issue
> http://stackoverflow.com/questions/22936749/optimistic-mode-for-gridgain-transactions.
> I added more simple test to the GridCacheTxMultiThreadedAbstractTest.
> Original test is also attached to the ticket. Sometimes commit fails with
> GridCacheTxOptimisticException, but two threads still can commit duplicated
> values so that increment is lost.
> see GG-8063
> Next test(s) should be unmuted on TC: testOptimisticSerializableConsistency
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
