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

ClusterExpirationManager missing locking

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 8.2.0.Beta2, 8.2.0.Final
    • 8.1.0.Final
    • Core
    • None

      Because ClusterExpirationManager.handleLifespanExpired() doesn't lock the entry and the value is actually read in the async thread, the created RemoveExpiredCommand sometimes uses a newer value written by another thread.

      Could be fixed by using DataContainer.compute() to check expiration and create the RemoveExpirationCommand.

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

              Created:
              Updated:
              Resolved: