[jira] [Comment Edited] (IGNITE-1092) GridCachePartitionedFailoverSelfTest hangs periodically because of timeout

["Semen Boikov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635189#comment-14635189 ] 

Semen Boikov edited comment on IGNITE-1092 at 7/21/15 2:37 PM:
---------------------------------------------------------------

Fixed hang with error ('Failed to wait for locks release future'): IgniteTxManager.finishTxs did not return rolling back optimistic transactions.


was (Author: sboikov):
Fixed hang with error ('Failed to wait for locks release future'): IgniteTxManager.finishTxs did not return rolling back optimistic transactions. But some cases in GridCachePartitionedFailoverSelfTest still can hang because of hanging GridNearOptimisticTxPrepareFuture, looks this hang reprodices only with near cache enabled.

> GridCachePartitionedFailoverSelfTest hangs periodically because of timeout
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-1092
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1092
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Denis Magda
>            Assignee: Semen Boikov
>             Fix For: sprint-7
>
>         Attachments: Ignite_Tests_Ignite_Cache_Failover2_98.zip
>
>
> The error after which the test start hanging:
> {noformat}
> ][ERROR][main][root] Test has been timed out and will be interrupted (threads dump will be taken before interruption) [test=testConstantTopologyChange, timeout=180000]
> {noformat}
> The log is attached.



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