[infinispan-issues] [JBoss JIRA] (ISPN-836) Three nodes leading in replication timeout exception.

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus resolved ISPN-836.
--------------------------------

    Resolution: Out of Date


This should be solved by the single node locking scheme in Infinispan 5.1: http://infinispan.blogspot.ro/2011/11/single-lock-owner-important-step.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+Infinispan+(Infinispan)
                
> Three nodes leading in replication timeout exception.
> -----------------------------------------------------
>
>                 Key: ISPN-836
>                 URL: https://issues.jboss.org/browse/ISPN-836
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Locking and Concurrency
>    Affects Versions: 4.2.0.CR4
>         Environment: Windows XP, 4.2.0-CR4 and 5.0.0-20101211.004348-5
>            Reporter: Thomas Jean
>            Assignee: Manik Surtani
>         Attachments: AgentManager_InfiniSpan_Config_Generic.xml, log4j_Generic.properties, nodeDeadLock-29627.log, nodeDeadLock-33969.log, nodeDeadLock-49482.log, ThreeNodesDeadlocks.java
>
>
> Hello,
> after activating deadlock detection with 500 ms of spin duration, i launch a concurrent scenario on three nodes.
> Each node will : begin the transaction,  lock the same key, perform a get and increment operation, commit the value.
> If a DeadlockDetectedException occurs, then the transaction rollback and the operation is immedialty retried in a new transaction until succeed.
> Then this exception occurs on two nodes :
> ERROR 15/12/10 15:49:08,791 [    main] interceptors.InvocationContextInterceptor     - Execution error:
> org.infinispan.util.concurrent.TimeoutException: Replication timeout for nodeDeadLock-29627
>         at org.infinispan.remoting.transport.AbstractTransport.parseResponseAndAddToResponseList(AbstractTransport.java:49) 
>         ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira