[
https://issues.jboss.org/browse/ISPN-9107?page=com.atlassian.jira.plugin....
]
Pedro Ruivo commented on ISPN-9107:
-----------------------------------
what configuration are you using?
READ_COMMITTED doesn't work in clustered environments. If the key isn't available
locally, it won't perform any database read neither a remote call to re-fetch the
value. But it should work in local caches.
why running long read-only transactions? can't the reads be performed outside a
transaction?
IsolationLevel.READ_COMMITTED does not work as expected
-------------------------------------------------------
Key: ISPN-9107
URL:
https://issues.jboss.org/browse/ISPN-9107
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.0.1.Final, 9.2.1.Final
Reporter: Tihomir Daskalov
Attachments: InfinispanTest.java
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.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)