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

Deadlock detection should be able to used with eager locking

    XMLWordPrintable

Details

    • High

    Description

      (As described on the forums):

      With a cache that explicitly (eagerly) locks a key and deadlock detecting –

      If transactions operating on a different node try to lock the same key, Infinispan will detect the deadlock. However, it can't interrupt the deadlock, so the transaction ends up timing out.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. ISPN-597 Deadlock detection and explicit locking should be enabled/allowed.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-596 Deadlock detection and explicit locking should be disallowed.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              mircea.markus Mircea Markus (Inactive)
              esalter@synamedia.com Erik Salter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: