[infinispan-issues] [JBoss JIRA] (ISPN-2849) Don't keep threads blocked when waiting for locks to be released

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988867#comment-12988867 ] 

Dan Berindei commented on ISPN-2849:
------------------------------------

My comment about TopologyAffectedCommands was fixed with ISPN-3527.

> Don't keep threads blocked when waiting for locks to be released
> ----------------------------------------------------------------
>
>                 Key: ISPN-2849
>                 URL: https://issues.jboss.org/browse/ISPN-2849
>             Project: Infinispan
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core
>    Affects Versions: 6.0.0.CR1
>            Reporter: Mircea Markus
>            Assignee: Pedro Ruivo
>
> ATM if a tx2 waits on a lock to be released by tx1, the (incoming) tx2 thread is BLOCKED and taken out from the pool. A better way to implement this is by using a structure that would hold and order the depending transactions on the receiver correlated with the async execution API from JGroups 3.3.0, result being that tx2 would not BLOCK but return to the pool this (not maxing out the thread pool that executes commands).
> More about it in the "Async invocation section" of https://docspace.corp.redhat.com/docs/DOC-134411 



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)