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

AtomicHashMap.put is not atomic with pessimistic locking

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 5.3.0.CR2, 5.3.0.Final
    • 5.2.7.Final, 5.3.0.Beta1
    • Core
    • None
    • Workaround Exists
    • Hide

      Use AdvancedCache.lock to lock the atomic map key explicitly before modifying it.

      Show
      Use AdvancedCache.lock to lock the atomic map key explicitly before modifying it.

    Description

      When the user calls AtomicHashMap.put(k, v), AtomicHashMapProxy.getDeltaMapForWrite() first reads the atomic map in the invocation context, and only acquires a lock afterwards.

      Between the read and the lock, another transaction can write something to the atomic map, and that write will be lost.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. ISPN-3736 Backport to 5.2.x for EAP 6.3

          • 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

              dberinde@redhat.com Dan Berindei (Inactive)
              dberinde@redhat.com Dan Berindei (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: