[ https://issues.jboss.org/browse/WFLY-6096?page=com.atlassian.jira.plugin.... ] Stephen Fikes updated WFLY-6096: -------------------------------- Description: When Infinispan 8.1 is incorporated in WildFly (WFLY-6094), the changes added as part of ISPN-5876 should be made non-default. For the databases that default to read blocking on modified rows (e.g. SQLServer) and for applications which can be designed to support pessimistic locking for all reads, the changes reduce the level of data integrity that can be guaranteed. As discussed in ISPN-5876, for databases which do not default to read blocking on modified rows or applications which cannot tolerate the cost of pessimistic locking, the changes address the case where stale data may be loaded and retained until explicitly evicted or timed out. Though the second case _may_ be the more common, it seems like the default should be to not reduce the integrity guarantee. was: When Infinispan 8.1 is incorporated in WildFly (WFLY-6094), the changes added as part of ISPN-5876 should be made non-default. For the databases that default to read blocking on modified rows (e.g. SQLServer) and for applications which can be designed to support pessimistic locking for all reads, the changes reduce the level of data integrity that can be guaranteed. As discussed in ISPN-5876, for databases which do not default to read blocking on modified rows or applications which cannot tolerate the cost of pessimistic locking, the changes address the case where stale data may be loaded and retained until explicitly evicted or timed out. -- This message was sent by Atlassian JIRA (v6.4.11#64026)