[
https://issues.jboss.org/browse/ISPN-2849?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2849:
------------------------------------
Same problem when a TopologyAffectedCommand arrives with a topology id smaller than the
current topology id. The command will block until the new topology is installed, but we
could instead hold all these commands in a queue and send them to the thread pool only
when we have the expected topology id.
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
Affects Versions: 6.0.0.Final
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 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