with syncCommitPhase=false, the CommitCommand is sent asynchronously. the TransactionCoordinator sends immediately the TxCompletionNotificationCommand that can be deliver first than the CommitCommand. The CommitCommand fails silently:
This bug affects the 5.3 and 5.2.5. I've made one test case to catch this bug:
Note: this bug may happen if you use async communication (prepare in 1PC)
Note2: this may be related to https://issues.jboss.org/browse/ISPN-2719
- do not allow to configure the cache with syncCommitPhase=false && recovery enabled;
- force syncCommitPhase=true when recovery is enabled;
- send the CommitCommand and the TxCompletionNotificationCommand as Regular Messages (they will be deliver in FIFO order)
Thanks to Diego Didona that spotted this bug.