Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-2849

Don't keep threads blocked when waiting for locks to be released

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 8.0.0.Beta3
    • 6.0.0.CR1
    • Core
    • None

      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

        1.
        		 Create timeout scheduler executor Sub-task Closed Major Pedro Ruivo
        2.
        		 Make BlockingTaskAwareExecutorService.checkForReadyTasks() asynchronous Sub-task Closed Major Pedro Ruivo
        3.
        		 Create Notifier Sub-task Closed Major Pedro Ruivo
        4.
        		 Refactor PerCacheInvocationHandler Sub-task Closed Major Pedro Ruivo
        5.
        		 Create CommandUUID Sub-task Closed Major Pedro Ruivo
        6.
        		 Create PendingLockManager Sub-task Closed Major Pedro Ruivo

            pruivo@redhat.com Pedro Ruivo
            mircea.markus Mircea Markus (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: