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

Prevent user from configuring passivation with a shared store

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.2.4.Final
    • Fix Version/s: 9.4.0.CR3, 9.4.0.Final
    • Component/s: None
    • Labels:
      None

      Description

      Passivation only makes sense with a non shared cache store. -The problem is that if an entry is passivated on a shared cache store only the first node will be able to activate the entry and subsequent nodes will always see null.-

      Looking closer the bigger issue is if an entry becomes passivated and then subsequently written to you will have a different value in the store as you would in memory.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                william.burns William Burns
                Reporter:
                william.burns William Burns
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: