Commit should fail if cache is in degraded mode ----------------------------------------------- Key: ISPN-8453 URL: https://issues.jboss.org/browse/ISPN-8453 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.1.9.Final, 8.2.8.Final, 9.1.2.Final, 9.2.0.Alpha2 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Major Fix For: 10.0.1.Final When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully. I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost.