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

Explicit Locks should throw AvailabilityException during ClusterPartition instead of Timeouts

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 15.0.0.Final
    • 11.0.5.Final, 12.0.0.Final
    • Clustered Locks, Core
    • None

      It seems that locks explicitly set by the application with lock(key) are not considered in case of active partition handling (the cache is in DEGRADED mode).

      In that case it will be still a timeout to aquire the lock, but it would be preferable to throw an AvailabilityException immediately instead of a TimeoutException after 30 seconds.

      The AvailabilityExcetpion is (only) thrown in case of put or get requests.

              rh-ee-jbolina Jose Bolina
              rhn-support-wfink Wolf Fink
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: