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

IsolationLevel.READ_COMMITTED does not work as expected

    XMLWordPrintable

Details

    • Bug
    • Status: New (View Workflow)
    • Major
    • Resolution: Unresolved
    • 9.0.1.Final, 9.2.1.Final
    • None
    • None
    • None
    • Hide

      See the attached standalone test that reproduces the issue. This test works with Infinispan 7.2.4, but fails with 9.0.1 and 9.2.1.

      Show
      See the attached standalone test that reproduces the issue. This test works with Infinispan 7.2.4, but fails with 9.0.1 and 9.2.1.

    Description

      We use Infinispan in JBoss EAP 7.0.9 as separate module. We use it in TRANSACTIONAL mode with READ_COMMITTED isolation level. After we upgraded Infinispan from 7.2.4 to 9.2.1, we notice that Infinispan does not obey the isolation level. It always behaves as REPEATABLE_READ.

      I see a similar issue in ISPN-1340 that is rejected with the argument that REPEATABLE_READ is a stronger isolation level than READ_COMMITTED and thus the later is not really needed.
      I see this as a feature loss. Our application has long-running transactions that only read from the cache and short-running transactions that read and write. This bug causes the long-running transactions to not see the changes from the short-running transactions. So, they do not profit from the cache and are slower.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tihomir.daskalov Tihomir Daskalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: