Details
-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
10.0.1.Final
-
None
Description
If we bring up one server and let it start to write to an invalidation_sync cache with putForExternalRead within a transaction, on bringing up another server which doesn't write to the cache we will get exceptions thrown on the commit of the transaction as the second server is coming up. If we use a 'put' it does not cause the issue and if it is a DISTRIBUTED_SYNC it doesn't cause the issue.
I have tried to write this test as an infinispan test but this doesn't show the issue, on trying the EmbeddedTransactionManager in my own test it also did not show the issue so I assume it has something to do with the limited nature of the EmbeddedTransactionManager.